News for hackers. Stuff that matters.
Re:uBlock Origin: Address first-party tracker blocking by TonyTheSlayer on Wednesday November 20, 2019 @06:54AM (#21583081)
Devil's advocate: then instead of using subdomains with randomly generated strings, we use words from a dictionary instead.
Re:uBlock Origin: Address first-party tracker blocking by roptat on Thursday November 21, 2019 @05:07AM (#21592765)
that won't work: for instance https://twitter.com/aeris22/status/1193644687950860289 (securite means security/safety in French, but that subdomain is a CNAME for smartadserver)
Re:uBlock Origin: Address first-party tracker blocking by Moru on Wednesday November 20, 2019 @07:10AM (#21583162)
Then we block those words :-)
Re:uBlock Origin: Address first-party tracker blocking by 0xC0ncord on Wednesday November 20, 2019 @07:18AM (#21583222)
You would have to block entire wordlists to combat subdomains like that. It would make more sense to whitelist subdomains instead, but it would require much more effort in order to determine what subdomains are required for the website to function. Additionally, if the site in question ever decided to change anything around, someone would have to catch the breaking change and have it corrected on the whitelists for the site to function again.
Re:uBlock Origin: Address first-party tracker blocking by squiggleblaz on Wednesday November 20, 2019 @08:21AM (#21583639)
How do you know what words to block?
Re:uBlock Origin: Address first-party tracker blocking by ekianjo on Wednesday November 20, 2019 @08:40AM (#21583760)
Machine learning by analyzing what displays on the page by blocking different domains. Bots can be automated to do that continuously and update a decentralized database with such information.