3 ms·
Ditched Chrome for FireFox years ago. But now I get increasing concerned on the direction Mozilla is moving towards. A couple of recent moves: 1. Pockets and Ac
by mrjin 5y ago
Ditched Chrome for FireFox years ago. But now I get increasing concerned on the direction Mozilla is moving towards.
A couple of recent moves:
1. Pockets and Accounts.
2. Unique Ids on installer downloads.
3. DNS over HTTP push.
All those moves can directly be linked to user tracking and I just feels something like "Block others and allows myself and myself only to track". So far I've no evidence to support it but let's wait and see.
- kibwen 5y agoThere are reasons not to like DNS over HTTP, but it's not there to let Mozilla track you. We have had ample evidence for years that ISPs have been using your unencrypted DNS traffic to track and profile you. Providing DNS over HTTP out of the box makes it easier for users to configure the browser based on their own threat model (Cloudflare is the default DoH target, but you can also provide your own).
- mrjin 5y agoYes, I fully understand the context and that's why I mentioned as it could be used to track us rather than was used to track us in the first place. Providing DNS over HTTPS can be deemed as goodwill as it indeed make it easier for some of the people. But making it default is something questionable, might be I remembered it wrong though. Pointing to Cloudflare does not make it any better as: 1. It can be changed anytime in the future and for most if not all users, they can hardly tell if there were changes to their DNS settings. 2. As end users, we have no idea what's the deal behind the scene between Mozilla and Cloudflare, and what was Cloudflare doing with the data collected. I might have worried too much about it for now. But at least, such move broke the design principle as DNS was never meant to be concerns at application level.