1271
Google Chrome pushes ahead with targeted ads based on your browser history
(www.theregister.com)
this post was submitted on 06 Sep 2023
1271 points (98.4% liked)
Technology
60082 readers
2622 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Another answer: Netflix
While the Mozilla foundation had designed browser DRM that worked on Linux, Chrome has the first implementation. And that enabled Linux users to watch Netflix.
Next one: forced fucking cloudflare DNS over HTTPS. I dipped Firefox because of that.
As shitty as google behaved, that was a nono
Could you give me an eli5 on the DNS part?
Sure, Firefox introduced a security feature: DNS over HTTPs. So instead if asking some DNS server that is configured on the local system, for the IP that belongs to a Domain name, am external service is asked via HTTPs.
While this is in theory a good idea, and has some benefits, the Firefox implementation was bad:
Users, that where forced into DNS over HTTPS could no longer resolve internal hostnames. This was a killer in office environments. And after the fix for that, everything was first submitted to cloudflare and only if cloudflare could not resolve the hostname, the local DNS server was asked, leading to potential information leaks. Also a no go for companies.
Firefox has fixed these issues by providing privacy policies, the option to choose other DNS over HTTPS providers and the option to define what domains should never be resolved externally.
But they lost trust in many professional environments because of that move.
Thank you. Yeah that sounds like a really bad move on their part.
I totally forgot one essential fact: the reason for DNS over HTTPS itself was perfectly valid: ISP's in the US are using DNS lookups of their customers for advertising. The idea is to prevent this kind of privacy breach. And it is very effective against it.
Just rye ideological driven implementation was bs