Gregory's Server@SwiftOnSecurity @AAKL Or maybe it's (past) time for people and devs to invest in blocking ads on the DNS level because browser-based is inevitably on the way out thanks to Google. https://mastodon.sdf.org/@joeo10/112968226631055809
|
5 comments
 @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. @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.  @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.  |
@joeo10 @SwiftOnSecurity @AAKL DNS based blocking will never be enough, when the owners of the internet (Google, Facebook, Amazon, Microsoft) are the same companies tracking you and serving you ads. You need to control the browser to have a chance to differentiate between good and bad traffic.