Live data from Hacker News

EasyList is in trouble and so are many ad blockers

adguard.com

431–439 of 439 posts

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

#431
post #430

Earlier quoted context omitted.

There are all sorts of games people could play, as a DoS is technically an act of war under some legal systems. For example: 1. take the top 200 most popular websites in the given nuisance area 2. add ban rules to a version-B list that also includes all social media, search engines, and Wikipedia. 3. Look at the user-agent string for that specific problem client, or extreme apikey quota abuse 4. Randomly serve versio…

Even then I would not do this without clearing it with a lawyer first. You could still end up at the wrong end of a lawsuit that you'll have to defend in India.

There are numerous legal/accounting specialists that protect businesses and investment decisions. We already won't serve _any_ content to IN networks as business policy... so are unlikely to ever have to visit with the cobras.

Have a gloriously wonderful day =)

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

#432
post #430

Earlier quoted context omitted.

Even then I would not do this without clearing it with a lawyer first. You could still end up at the wrong end of a lawsuit that you'll have to defend in India.

There are numerous legal/accounting specialists that protect businesses and investment decisions. We already won't serve _any_ content to IN networks as business policy... so are unlikely to ever have to visit with the cobras. Have a gloriously wonderful day =)

Not serving means there is already no content. That is different to serving 100TB of 404 content from clients that will never stop.

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

#433
post #330

Earlier quoted context omitted.

Generally, I like the idea with the user agents filtering and “block everything” rule. No need for geoblocking. Insert a comment about why this is happening and ask for it to be changed. However, as we’re living in the real world and the authors of the respective browsers strike me as lazy or uninterested, I also bet all that would change is the user agent.

"User agent" is a synonym for "browser". When you say "user agent" here, what you really mean is the contents of the header that identifies the user agent, i.e., browser. Calling it that is a little bit like referring to Chrome's developer tools as "Inspect Element" (based on the mistake that that's supposed to be its name, rather than recognizing that the label is just a simple, descriptive verb/action).

No post body was provided.

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

#434

Earlier quoted context omitted.

> it's cloudflare deciding to protect "web content" and not videos or .iso images or other things that normally are not commonly served while you browse a contemporary website and read HTML. That's false in two ways: first, text is normally served while you browse a contemporary website; second, so are images, which are explicitly called out as potentially violating this clause. Text is the only data that isn't cover…

Quoted post unavailable.

[deleted]

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

#435

Earlier quoted context omitted.

> like 0.005c/gb You're off by a factor of 100. https://www.belugacdn.com/cdn-pricing/ $5000/PB = $5/TB = 500c/TB = 0.5c/GB

beluga > You pay 1¢ (or less!) for every Gigabyte of data accelerated over our cloud network. doesn't seem clear cut as they bundle it in a subscription packages, but at this volume you'd surely need their enterprise package (10Tb+), which you'd expect to get 0.01 or less bunny > First 500TB $0.005 /GB > From 1PB-2PB $0.002 /GB

You wrote 0.005c not $0.005

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

#436
post #33

I'm confused about the ToS comment by Cloudflare. The txt is on a website so it is a web content? So robots.txt is not supported by Cloudflare to cache/proxy it? That would be a weird regulation. And I bet everyone violates the Cloudflare ToS then.

It's from this tos page: https://www.cloudflare.com/terms/ 2.8 Limitation on Serving Non-HTML Content ...Use of the Services for serving video or a disproportionate percentage of pictures, audio files, or other non-HTML content is prohibited, unless purchased separately... A huge text/plain artifact, requested often, would seem to fall into that category of "disproportionate percentage" compared to text/html served.

From a legal perspective I can understand such a wording, but I wonder why an engineer simply tells a (non-paying) customer that he violates the ToS, without thinking about it.

I mean, one could simply wrap the content in a HTML body and change the extension, but that would actually increase the data load for no good reason. So it is complete non-sense to complain about txt files being served.

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

#437
post #424

Earlier quoted context omitted.

I am following up internally. Looks like there's a combination of this data not being cached, our systems thinking a DDoS was happening (which it sort of was). But getting the full story now.

Seems like MP says it’s fixed: https://twitter.com/tuinslak/status/1583016022491435009?s=61...

I'm glad they sorted it out, but I wish there was a proper support route other than "create a sufficient media storm so that an employee tweets the CEO"

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

#438

Earlier quoted context omitted.

beluga > You pay 1¢ (or less!) for every Gigabyte of data accelerated over our cloud network. doesn't seem clear cut as they bundle it in a subscription packages, but at this volume you'd surely need their enterprise package (10Tb+), which you'd expect to get 0.01 or less bunny > First 500TB $0.005 /GB > From 1PB-2PB $0.002 /GB

You wrote 0.005c not $0.005

my bad, not native speaker

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

#439
post #157

Earlier quoted context omitted.

A filter list is definitely not HTML

The minimal spec valid HTML5 document is currently: a Practically, browsers will accept omitting both of these, and the spec even allows for omitting the title "if it is provided by a higher level protocol" So it's not that crazy an argument that a plain text file is a html document

Only because they've so comprehensively defined HTML parsing that even parsing random data has a well-defined result.
Post reply on HN