@uzayran @SwiftOnSecurity @AAKL Sadly, DNS ad blocking...

SwiftOnSecurity's posts Post Back to profile

@uzayran @SwiftOnSecurity @AAKL Sadly, DNS ad blocking is going to be the best we got unless governments start waking up and smell the coffee plus do something to reign in on these tech giants.

Like 19 August at 17:26 | Wall-to-wall | Open on mastodon.sdf.org

2 comments

hackyspice

@joeo10 @uzayran @SwiftOnSecurity @AAKL For casual readers that don't manage DNS filtering daily, uzayran is saying you can probably get away with blocking ads.youtube.com now because probably that's just ads and not videos.

But eventually, ads could be served from videos.youtube.com and feed.facebook.com, the same domains that serve content, which you will probably not block. Then we are back to our crippled in-browser filtering.

19 August at 18:38 | Open on infosec.exchange

uzayran

@hackyspice @joeo10 @SwiftOnSecurity @AAKL that is a good explanation, with the caveat that it already is not possible to block Youtube ads (or Twitch, or Prime Video etc) on the DNS level. It currently works well enough in a combined approach with in-browser blocking (or in-application more broadly). But as soon as we have to rely on DNS-filtering alone, it will be a losing battle.

19 August at 19:00 | Open on cyberplace.social

Go Up