Comment Re:Gray areas? (Score 1) 56
Equating "opt-in" with "just don't use these UI elements" is too coarse-grained to be a useful rule of thumb. At the top of that slippery slope is stuff like freemium applications - until you give them a credit card, various buttons/features just show you an ad and a buy button. I think this is perfectly acceptable, even if it feels a bit tacky to me. But once you accept getting a little more adversarial with your UX design, it isn't all that far from arranging buttons such that you can count on a predictable percentage of misclicks, Zuckerbook-style privacy-settings, and other shitty behavior like that.
I'm not some gnu-eyed idealist, but I do expect software I run on my machine to behave in ways that align (or can be made to align) with my slightly idiosyncratic interests. Software that behaves like a tireless nagging 3 year-old or tries to trick me in to doing what the developer wants is garbage that doesn't belong in my house.
It is harder to express, but I really think the bar for an application like Firefox needs to be, good-faith accommodation of a very wide range of people, in basically every relevant dimension, which is a lot, because browsers touch nearly everything. "I don't want to (I don't want my kids/people at this kiosk/whoever to) interact with your robots" is a perfectly reasonable accommodation to make. None of this is new - discussion about (un)ethical patterns of human-computer interaction goes back decades.
Now think about having this same argument over a feature that inserts free clipart into documents or saves the current page to a clipping service. The fact that this sort of discussion about UI is even controversial is a testament to how much the money people are desperate to shovel this stuff at you are.