I assume this is a large reason why websites are so keen for you to use their apps.
I assume this is a large reason why websites are so keen for you to use their apps.
Instagram doesn’t really work outside of the app for me though
i get buffering on a regular basis, videos take multiple seconds to get started.
libretube OTOH is much better.
been using newpipe since it came out first so i have seen the whole drama of previous many years.
It works inside Apps (Android etc.) and games or youtube videos, too. There are ways to get around this, like e.g. hardcoding IPs that are not known to serve Ads, but this needs additional work and 99% of ads don't do this. Benefits of router based DNS sinkholes:
- cannot be detected by websites with anti-adblock scripts
- no memory consumption on clients
- fewer web browser plug-ins needed
- lower device CPU utilization from AdGuard PC/Android apps, uBlock extensions etc.
- protects all network devices without requiring extra work
- browser, software and OS independent
- device and PC independent.
- implements redundancy should users remove/disable browser plug-ins
[1]: https://next-episode.net/The reason why this does not happen is that companies understand that someone who hates ads so much they are willing to deploy an ad blocker, a DNS sinkhole, etc will probably not click on an ad either way.
The only actual direct consequence to clients I have noticed is that if you directly want to resolve Blocked-Ad-Links, it won't work - e.g., Google usually displays some "Ad"-Links first as results - clicking these won't get you anywhere. For my private LAN users, I think this is a good lecture to have - realizing that you're bullied into clicking valid-looking links that are instead Ads, from people that pay others to distract you from what you were actually looking for, or distort the natural ranking by paying for being ranked first.
I have a printout at our house for visitors who complain about this: They can manually set their DNS to 8.8.8.8 and my router won't interfere (it could, but I found spoofing direct requests to Google's DNS a bit too much).
Loading faster is also probably detectable, especially if there's some request that the server intentionally replies slowly to to aid detection.
I use nextdns (because I was too lazy to setup pi-hole), which has a simple ui for whitelisting domains as and when I can’t get around one (though usually it’s down to a tracking script breaking a site when it fails to load).