[unloader6118]

> When it happens only a few times, it might be neglect. This is absolutely by design.

Not sure if I want to call it by design.

It is not a dark pattern, it is just "what is the minimum we can do to sell this without doing the curation work?"

[toss1]

Building 29 separate settings with confusing and overlapping effects is less work than making a single setting of: [Local Only]?

Seems to be a much larger amount of work to design, implement, and support a more-or-less dozen-step customer journey that does NOT work than just implementing a few switches. And that goes even if the switch must be designed-in from the beginning by designing operation for local-only operation.

Surely, implementing a simple block-all-strangers to send-to-bitbucket all communications attempts by accounts not already on the whitelist is easier than all these overlapping settings described?

Unless it is explained how building a much more complex system is easier and lower-cost than a simpler system with fewer controls, the default conclusion is it is intentional.

>>It is not a dark pattern, it is just "what is the minimum we can do to sell this without doing the curation work?"

Even if for the sake of discussion we treat it as laziness, a dark pattern created by accident is still a dark pattern. The customer is no less screwed into doing something they do not want and the company does want.

[pwg]

> Building 29 separate settings with confusing and overlapping effects is less work than making a single setting of: [Local Only]?

The 29 separate confusing overlapping effects is by design. A single "local only" switch would (so long as that switch is enabled) lock out all manner of potential future revenue and recurring rents, which these companies very much want to see hit the balance sheet.

So the 29 separate confusing overlapping settings is designed to frustrate you to the point that you allow what they want from the start, the ability of the device to generate future revenue (via both of one time sales and recurring rents on rental sales).

[quirkot]

>> Building 29 separate settings with confusing and overlapping effects is less work than making a single setting of: [Local Only]?

Yes, absolutely. 29 separate overlapping settings likely match up precisely to arguments in various APIs that are used. On the other hand, what does local only even mean? No wifi? No hardwired connection? LAN only? Connection to the internet for system updates but not marketplace? Something else? All with a specified outcome that requires different implementation depending on hardware version and needs to be tweaked everytime dependencies change.

[gukov]

I’m not sure why some are struggling to understand this. A single "godmode" checkbox would only be possible if every element, the marketplace, the hardware, and the payment rails, were inside one ecosystem. The Switch is Nintendo, Minecraft is Microsoft, the credit card is Visa, and so on. There are simply too many moving parts, making a single killswitch nearly impossible to orchestrate.

[toss1]

Of course, making one single switch for everything in that complex system is absurd. Which is why this is something no one is talking about here.

We are only talking about the architecture, setup, and options for each particular game.

[senordevnyc]

Because raging online at evil corporations feels better than facing the complexity of the world

[Ajedi32]

That, or an open standard.