Guster@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · 8 months agoFacepalmlemmy.worldimagemessage-square231fedilinkarrow-up11.17Karrow-down173
arrow-up11.1Karrow-down1imageFacepalmlemmy.worldGuster@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · 8 months agomessage-square231fedilink
minus-squareDojan@lemmy.worldlinkfedilinkEnglisharrow-up2·edit-28 months agoPossibly something like PiHole? Though I’ve not tried that myself.
minus-squareRobmart@lemm.eelinkfedilinkEnglisharrow-up15·8 months agoPiHole doesn’t work on YouTube ads unfortunately. No DNS based blocker does.
minus-squaredan@upvote.aulinkfedilinkEnglisharrow-up2·8 months agoThis is generally the case for any sites thay have their own ad inventory, since the ads are coming from the same servers as the site itself.
minus-squareAniki 🌱🌿@lemm.eelinkfedilinkEnglisharrow-up1·8 months agoActually this is true with anything closed sourced since they are probably using their own internal, encrypted DNS look-ups. FOSS fixes that.
minus-squaredan@upvote.aulinkfedilinkEnglisharrow-up1·8 months agoThey don’t even need to do that, since the ads come from the same domain as the app’s content. Some apps use their own DNS resolver but a lot of the time it’s for other reasons, like preventing DNS hijacking by ensuring DNSSEC records are validated.
Possibly something like PiHole? Though I’ve not tried that myself.
PiHole doesn’t work on YouTube ads unfortunately. No DNS based blocker does.
This is generally the case for any sites thay have their own ad inventory, since the ads are coming from the same servers as the site itself.
Actually this is true with anything closed sourced since they are probably using their own internal, encrypted DNS look-ups.
FOSS fixes that.
They don’t even need to do that, since the ads come from the same domain as the app’s content. Some apps use their own DNS resolver but a lot of the time it’s for other reasons, like preventing DNS hijacking by ensuring DNSSEC records are validated.