lemmylommy@lemmy.world 3 weeks ago
Some ads have used browser exploits to infect visitors in the past. So this is a very, very bad idea, if it actually is implemented in a way that is hard to filter for ad networks.
lemmylommy@lemmy.world 3 weeks ago
Some ads have used browser exploits to infect visitors in the past. So this is a very, very bad idea, if it actually is implemented in a way that is hard to filter for ad networks.
DarkSurferZA@lemmy.world 3 weeks ago
So the way I understand this to work, it’s 100% safe from the type of attack you’re describing.
You are clicking the link (asking the advertiser for the data) but then never actually fetching it.
So you can never get the malicious payload to be infected.
Goretantath@lemm.ee 3 weeks ago
Im too scared to trust it works out fine in the end to use it, been raised on the idea that interacting with an ad in any way other than task managering the pop up is dangerous. Wheres the part of the code that makes it safe and a write up of how it functions, otherwise im fine just blocking ads with regular ublock.
lime@feddit.nu 3 weeks ago
the part that’s safe is in the browser. it’s a basic fact of how http requests work that you can just request data and then not read it.
also, “task managering the popups”? unless i’ve missed some very weird development that has literally never worked, because popup windows are part of the parent process.
medgremlin@midwest.social 3 weeks ago
Back on Windows 98 through XP, each individual window was a process that could be killed in Task Manager, and popups opened in a new window.
doodledup@lemmy.world 3 weeks ago
What makes you think uBlock is safe without checking relevant code sections?
techt@lemmy.world 3 weeks ago
Here you go, from the repo:
That’s pretty much it! Let me know if it doesn’t make sense, I can annotate it