[oehpr]

Has anyone figured out why so many corps do this? It always feels like it's one step from:

* Of course do whatever you want! * Nah I'm a big dumb idiot who doesn't know whats good for him so ask me in 3 days when I've hopefully come to my senses.

I think a simple law would fix this

If no wasn't an option, you did not establish consent.

[kotaKat]

[flagged]

[nitwit005]

Management that struggles to acknowledge their users don't like something they wanted built.

They'll definitely realize their mistake and turn on our amazing feature! (This unfortunately is the real attitude sometimes)

[xigoi]

You answered your own questions. They do think of their users as big dum idiots.

[mhitza]

Not only idiots. They bank on laziness. One time you enable something by mistake then you might not spend the time to find the well hidden option to disable it.

Which reminds me, anyone know the precise location where one would disable Google's Gemini on their account?

[thewebguyd]

> They bank on laziness.

And they would be correct. Less than 5% of users change defaults. That's why features get shoved in, on by default because if they didn't, very few would ever enable them. Not defending the practice, I hate it, but that's why they do it.

[rightbyte]

KPI hunting? Toxic/fake positivity?