Live data from Hacker News

EasyList is in trouble and so are many ad blockers

adguard.com

161–170 of 439 posts

Re: EasyList is in trouble and so are many ad blockers

#161

Earlier quoted context omitted.

A filter list is definitely not HTML

They host the zipped files of content for haveIbeenPwned for Troy Hunt...

That's a special project they decided to take on, not subject to the standard ToS.

Re: EasyList is in trouble and so are many ad blockers

#162
post #48

Earlier quoted context omitted.

Sounds like they’re just using the wrong service. R2 is designed for object storage, and has 0 egress fees. That’d be the way to go. Not sure why the support engineer didn’t mention it. The standard cloudflare web caching probably doesn’t work well for this use case for whatever reason. The price is only 0.015/GB/mo, so the ~MB(?) of list would be served in perpetuity for less than a dollar.

Actually, you're right. How would this work? Is Cloudflare really willing to foot the bill of 20 TB of bandwidth per day for a small text file that costs $0 to store?

Egress is free but not public i.e. you can't just give anyone an url. You have to use your own server to fetch content from R2 and then serve it to your visitors. Each fetch costs money but first 10 mil reads are free and your own server probably has egress fees.

Re: EasyList is in trouble and so are many ad blockers

#163

Bittorrent, switch in long-term to that. Not saying every end-user should be a seeder but there is big bittorrent community out there and everyone could help a little bit. Other options: - A kind of mirror network (it only needs to keep sure that integrity can be checked, maybe with a public key) - And while doing that why not also support compression (why not? only devs need to read it and they can run easily a deco…

Oh, but yes every user should be a seeder. Why not?

Re: EasyList is in trouble and so are many ad blockers

#164

Earlier quoted context omitted.

I'd agree that's weird. Seems like if it were simply renamed to .html with no content changes, then it would be okay. > What else is important to note that the client is being abused and not the client abusing the service. That should be taken into consideration, when deciding if someone is breaking the ToS. My understanding has this as moot. The issue from Cloudflare's perspective is only that the content is non-HTM…

> (i) serving web pages as viewed through a web browser or other functionally equivalent applications, including rendering Hypertext Markup Language (HTML) or other functional equivalents, and (ii) serving web APIs subject to the restrictions set forth in this Section 2.8. The key is "as viewed through a web browser" imo, this is not really an API and it's not a webpage; it's a datafile and would fall into R2 or simi…

I see, that makes the position more understandable. I guess the same rule would (should) apply if they did indeed simply change the extension.

Re: EasyList is in trouble and so are many ad blockers

#165

Earlier quoted context omitted.

Actually, you're right. How would this work? Is Cloudflare really willing to foot the bill of 20 TB of bandwidth per day for a small text file that costs $0 to store?

Egress is free but not public i.e. you can't just give anyone an url. You have to use your own server to fetch content from R2 and then serve it to your visitors. Each fetch costs money but first 10 mil reads are free and your own server probably has egress fees.

No, egress is indeed public. Here's an example link, straight to R2:

https://img.phantasmagoria.me/img/96XJrjejoHNdrQv7.jpg

Even if you have a private bucket, you can give people a signed link with read access, for up to two weeks, IIRC.

Re: EasyList is in trouble and so are many ad blockers

#166
1. Add a ToS to the EasyList website that prohibits this sort of abuse. (I don't see any currently.)

2. Send a cease and desist letter to the app creator.

3. If they don't respond, also send a C&D to Google demanding they cease distribution of the malware responsible for the DDoS.

Anyone can send a cease and desist -- it's just cautionary letter. You aren't obligated to follow through with the threatened legal action.

It doesn't have the force of law behind it, but it'll at least get their attention.

(IANAL)

Re: EasyList is in trouble and so are many ad blockers

#167
post #19

Phew. Is just a bandwidth issue. This goofy title made me think advertisers found a way around ad blockers.

In a way, the advertisers did find a way around ad blockers. Google built an entire browser and used Manifest V3 as an excuse to cripple ad blockers. Companies are also paying influencers, twitch streamers, and YouTubers to promote their products in a way that conventional ad blockers can't prevent.

In case anyone reading hasn't heard of it: SponsorBlock for YouTube - Skip Sponsorships - https://chrome.google.com/webstore/detail/sponsorblock-for-y...

Re: EasyList is in trouble and so are many ad blockers

#168

A great opportunity right now for CloudFlare to win some goodwill and PR by helping out EasyList for free right now. But what about simply enable a firewall and show captcha or similar if the origin IP is from India and requesting that URL until the situation is under control? I did that with the free plan recently in CloudFlare in a similar situation and it worked perfectly (of course on a much smaller scale).

I can't understand their argument that a text file 'isn't a web content'; seems like a bullshit excuse.

Re: EasyList is in trouble and so are many ad blockers

#169
post #74

Earlier quoted context omitted.

Determining file type from the file name suffix is a fool's game and always was.

Is it? Seems superior to arbitrary magic numbers or headers, and God forbid full naive parsing, in most ways.

I doubt there is any solution that is both robust and simple. In a sense, it is the same problem as that which ad blockers are attempting to solve.

Re: EasyList is in trouble and so are many ad blockers

#170

A great opportunity right now for CloudFlare to win some goodwill and PR by helping out EasyList for free right now. But what about simply enable a firewall and show captcha or similar if the origin IP is from India and requesting that URL until the situation is under control? I did that with the free plan recently in CloudFlare in a similar situation and it worked perfectly (of course on a much smaller scale).

I can't understand their argument that a text file 'isn't a web content'; seems like a bullshit excuse.

Does not inspire confidence in Cloudflare, that’s for sure.
Post reply on HN