AdguardTeam / AdGuardSDNSFilter

AdGuard DNS filter
https://adguard-dns.io/
GNU General Public License v3.0
823 stars 130 forks source link

Samsung/LG/Philips smart-TV ad(?) domains #830

Closed DandelionSprout closed 2 years ago

DandelionSprout commented 2 years ago

Steps to reproduce

N/A

Expected behavior

Both of the following: 1) AdGuard DNS begins promoting itself as having support for smart-TVs, for which there's a potentially huge market. 2) The current entries for smart-TVs get expanded as far as feasible.

Actual behavior

AdGuard DNS has (a heavily underadvertised) support for blocking smart-TV ads (Primarily on Samsung TVs), so I figured I'd add a few more entries based on https://blog.malwarebytes.com/privacy-2/2021/11/smart-tv-adverts-put-a-wrinkle-in-your-programming/ and https://raw.githubusercontent.com/Perflyst/PiHoleBlocklist/master/SmartTV-AGH.txt

I propose:

||ad.nettvservices.com^
||ad.lgappstv.com^
||lgad.cjpowercast.com.edgesuite.net^
||lgsmartad.com^
||ads.samsung.com^
||gpm.samsungqbe.com^
||samsungacr.com^
Screenshot: N/A

Your environment

Description Value
DNS server in use: https://filters.adtidy.org/windows/filters/15.txt
How did you setup DNS configuration: System
Device model: Samsung ≥2019 TVs in particular
Operating system and version: Tizen OS (unknown versions)
pgl commented 2 years ago

Just a quick note - some of these were already on my list, but now they all are.

Alex-302 commented 2 years ago

No need to add them. @ryanbr already added them to EL:) Just wait for DNS filter compiler.

pgl commented 2 years ago

Hey I got there first

xlionjuan commented 2 years ago

BLOCK "gpm.samsungqbe.com" this domain will cause my SAMSUNG Smart TV can't login Samsung account and make the device can't install any app on it. (But if you installed already, the installed app still works) I need to whitelisted this domain in order to use any Samsung SmartThing's feature.

DandelionSprout commented 2 years ago

Thanks for the headsup. Seems like https://twitter.com/mattpbarlow/status/1453751474836709376 was wrong about suggesting that people should block that domain, then.