this post was submitted on 28 Mar 2024
1183 points (99.3% liked)

Technology

59641 readers
4069 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] FlyingSquid@lemmy.world 21 points 8 months ago (11 children)

Don't a majority of them also use Chrome? Because they're going to find that their adblockers are less and less effective.

[–] IphtashuFitz@lemmy.world 11 points 8 months ago (10 children)

That’s yet another reason to use a DNS as blocker, and not let your browser use DNS over https.

I haven’t done it myself yet, but I figure that sooner or later I’ll need to update my router to block all outbound DNS that doesn’t go through my DNS ad blocker. Some devices try to use their own hardcoded DNS to get around them…

[–] dejf@lemmy.world 4 points 8 months ago (2 children)

Why shouldn't you let your browser use DNS over HTTPS?

[–] AA5B@lemmy.world 3 points 8 months ago* (last edited 8 months ago)

Because then it can bypass your ad-blocking DNS

DNS over HTTPS was a great idea for privacy if left in your hands, but immediately ran into the reality of intrusive advertising

[–] Hexarei@programming.dev 2 points 8 months ago

Because dns ad blocking is typically done with something like dnsmasq which doesn't support DNS over HTTPS, though it's easy enough to setup a resolver/forwarder that does

load more comments (7 replies)
load more comments (7 replies)