News for hackers. Stuff that matters.
Re:EasyList is in trouble and so are many ad blockers by mindslight on Wednesday October 19, 2022 @07:31PM (#33269130)
Actually you're missing the point. It doesn't seem like people are condemning Cloudflare for not serving a bandwidth-heavy file for free (FTA: "CloudFlare does not allow non-enterprise users use that much traffic").

Rather what's being condemned is this nonsense customer service characterization of a text file as somehow not "web content". Easylist.txt is a data file that could just as easily be in JSON (and be larger). Furthermore, as it stands easylist.txt actually looks like it's a valid text/html file, as browsers generally don't insist on <html>/<body> tags. So from both directions it seems like the customer service drone has thrown out this nonsense just to short circuit having to do their job.

Re:EasyList is in trouble and so are many ad blockers by manigandham on Wednesday October 19, 2022 @08:33PM (#33269537)
But it's not JSON or HTML. And it's not meant for browsers. It's clearly a dataset as a text file and not meant as "web(page) content". What's nonsense about that when it's completely accurate?
Re:EasyList is in trouble and so are many ad blockers by thayne on Wednesday October 19, 2022 @09:34PM (#33269883)
How is it any different from a json file used by a web app (or mobile app, or desktop app)?

And there is no reason a web app couldn't read data from a txt file instead of a json file.

Re:EasyList is in trouble and so are many ad blockers by manigandham on Wednesday October 19, 2022 @10:05PM (#33270041)
It's not for displaying a webpage but to power a separate application. Just because you can serve any kind of file over an HTTP connection doesn't mean it qualifies as the standard usage for serving a website. There's a reason Cloudflare also doesn't allow large video files either - even though that arguably counts as "web content" even more.

This is a rather straightforward and reasonable interpretation of the terms and it's strange to see such pushback.

Re:EasyList is in trouble and so are many ad blockers by thayne on Wednesday October 19, 2022 @11:11PM (#33270390)
But the support email didn't say it was a violation of the ToS because it is primarily used by non webpage applications (the ToS does say APIs may be allowed, but doesn't have specific details on when afaict), it says it is a violation because it is a txt file, and there is a txt couldn't be a part of a website. And in fact robots.txt and security.txt are standard and common txt files serves as part of websites. In the case if robots.txt it also is primarily consumed by web crawlers, not for actually rendering web pages. Does that mean robots.txt violates the ToS too?
Re:EasyList is in trouble and so are many ad blockers by yellowapple on Thursday October 20, 2022 @12:38AM (#33270872)
> There's a reason Cloudflare doesn't allow large video files either - even though that probably counts even more as "web content".

And that's just as nonsensical. Bytes are bytes; the rationale should be based on bandwidth, not on arbitrary micromanagement of the format of the data consuming that bandwidth. If I encode that video in a giant self-contained blob of JavaScript that feeds the pixels into a canvas or something similarly ridiculous, does that magically fix the bandwidth issues?

Re:EasyList is in trouble and so are many ad blockers by manigandham on Thursday October 20, 2022 @12:59AM (#33270992)
No. It is about excessive resources/bandwidth usage. The customer service response reply isn't great but the context itself is clear because this file is clearly not for displaying any part of the web presence of the easylist site.

Again this is that "pedantic technicality" - why such a fuss when the actual issue is straightforward, and also clearly understood and reiterated by the easylist team themselves in the post?

Re:EasyList is in trouble and so are many ad blockers by yellowapple on Thursday October 20, 2022 @02:25AM (#33271478)
> It is about excessive resources/bandwidth usage.

Then the policy would focus on that rather than micromanage the format of the data using those resources/bandwidth. Again: bytes are bytes.

> why such a fuss

Because a policy as nonsensical as "no non-HTML files allowed" artificially limits the usefulness of CloudFlare for precisely zero legitimate reason. I ask again: does wrapping a video in a blob of JavaScript fix the bandwidth issues associated with hosting videos? If I have a 10MB MP3 downloaded 1,000 times v. a 1MB HTML/CSS/JS static site downloaded 10,000 times, what difference does it make?

Re:EasyList is in trouble and so are many ad blockers by archi42 on Thursday October 20, 2022 @03:11AM (#33271707)
The difference is in the amount of cache you need. In one case you save 10GB per 1MB of cache, in the other just 1GB per 1MB and the big file is going to evict many small files (even if the user only listens to the first 10s). It's no huge difference for a single user/site, but across all users this quickly means needing a multiple of the current cache; which doesn't come for free.

Also, CF have a product to sell. The free tier is just the demo version: I think at the end of the day the policy is about not everyone in HN using CF for their low-cost DIY video and/or music streaming or download platform.

And I can totally see them reverse the decision and sponsor that project (it's probably something a support engineer has no power to decide).

Re:EasyList is in trouble and so are many ad blockers by thayne on Thursday October 20, 2022 @11:40AM (#33276378)
So have a max file size.

Also, the same ToS applies if you use the paid product. Unless you buy an additional addon for non-web traffic.

Re:EasyList is in trouble and so are many ad blockers by yellowapple on Thursday October 20, 2022 @01:43PM (#33278125)
> The difference is in the amount of cache you need.

Okay, now run the same thought experiment with 10,000 downloads of a 1MB MP3 v. 10,000 downloads of a 1MB HTML/CSS/JS site. What difference then?

Re:EasyList is in trouble and so are many ad blockers by manigandham on Thursday October 20, 2022 @08:39PM (#33282750)
The issue is about bandwidth and resources. The policy is generic to provide reasonable allowances but stop usage that's clearly outside the limits. That's how "unlimited* but with oversight" plans work.

Again, it's pretty clear what the file is actually for and how much bandwidth its using. It's not about bytes or file types at all.

Re:EasyList is in trouble and so are many ad blockers by LawTalkingGuy on Thursday October 20, 2022 @04:31AM (#33272118)
So the solution is to HTML the list and link it from the webpage?

> why such a fuss

Mockery isn't a fuss. And why? Because we can all picture having to deal with just this sort of idiot and their pet rule.

Re:EasyList is in trouble and so are many ad blockers by Spunkie on Thursday October 20, 2022 @01:36AM (#33271189)
> It's not for displaying a webpage

The majority of of legitimate traffic to these txt files are by browsers(extensions) for the express purpose of rendering websites to a users specifications(without ads in this case).

A reasonably low estimate is that 20%-30% of global internet users are behind some kind of adblocker, almost all of which are default subscribed to easylists. So this txt file is potentially responsible for the way BILLIONS of internet users see and interact with every single web site.

Cloudflares claim that this isn't web content is full on reality warping. It only makes any kind of sense when masked under layers of abstractions and lawyer speak.

Re:EasyList is in trouble and so are many ad blockers by 3np on Wednesday October 19, 2022 @09:34PM (#33269884)
oh it's for browsers all right
Re:EasyList is in trouble and so are many ad blockers by yellowapple on Thursday October 20, 2022 @12:34AM (#33270851)
> And it's not meant for browsers.

It literally is - specifically, for extensions thereof.

Re:EasyList is in trouble and so are many ad blockers by r3trohack3r on Thursday October 20, 2022 @09:58AM (#33274777)
I like the HN approach of taking a charitable interpretation of their message.

Clearly EasyList lived on their free tier for a long time without interruption. Only when they used excessive bandwidth did ToS enforcement happen. When they reached out for support, the support agent rightly pointed out that this isn't a website file.

Reading the ToS, the support agents message appears to be correct. Text files are fine (as is pretty much any format) as long as it isn't the main focus of the HTTP server Cloudflare is fronting. Robots.txt would be fine, turning the list into XML or HTML would not be fine. In this case, the text file isn't there to support the web content of Easy List - it's distributing a text file to applications.

The agent could have added additional context but their message is valid.

Re:EasyList is in trouble and so are many ad blockers by mindslight on Thursday October 20, 2022 @11:02AM (#33275814)
You're still conflating "free tier" with "not a web file". According to the article, they are separate issues in that Cloudflare wouldn't be willing to host easylist.txt even on a paid plan.

Meanwhile -

1. easylist.txt is used by every single web page I visit. So the overall purpose argument fails.

2. Web pages commonly use non-directly-renderable data files in formats like JSON or XML, so the file purpose argument fails.

3. Text files are and continue to be one of the major formats displayed by browsers. So the file type argument fails.

4. The size of the file is in line with other files cached by Cloudflare. So that argument fails.

If the Cloudflare support rep said "we just don't feel like doing business with you", that would be a different thing. But instead they're throwing out some arbitrarily-framed unfalsifiable reason as if it's a logical justification. And no, customer service drones and corporate policies don't deserve a fundamental benefit of the doubt, per contra proferentem (ambiguous terms should be construed against the drafter). It's impossible to know what they actually mean here besides "we don't like it", and that is the problem.