- cross-posted to:
- firefox@lemmy.world
- firefox@lemmy.ml
- cross-posted to:
- firefox@lemmy.world
- firefox@lemmy.ml
“Last month, Mozilla made a quiet change in Firefox that caused some diehard users to revolt…”
“Last month, Mozilla made a quiet change in Firefox that caused some diehard users to revolt…”
But why? Does it expose more data? More sensitive data than before?
What I don’t get, but maybe because of the lack of information I have on the topic is that if it’s better in terms of data privacy than before, or is it better if it’s turned on than off, why is it such a great problem, if it’s turned on by default? In this case, not turning it on would be something that one should be noted. Any technical, real-world reasons why not giving my consent to enable this feature gives reason to get mad, or is this really just about “not having a choice”, regardless the outcome?
Exactly. That’s also the issue there. It was opt-out by default AND didn’t seemed to give enough info to the end-user about what it does, and why it would be better to keep it enabled. Most people, complain about the forced default decision without any notice, and without any appropriate info to understand if it was a decent change or not. You should only enable it, IF you understand and ablige to what it does.
I understand this, thanks. But still feels way too overreacted. But now, that’s just what I think about this.