[laundermaf]

This issue caused CF to irreversibly ban them though, so it's not "just a bandwidth issue" anymore.

> Based on the URL that are being requested at Cloudflare, it violates our ToS as well. All the requests are txt file extension which isn't a web content

> you cannot use Cloudflare to cache or proxy the request to these text files

[jsty]

> This issue caused CF to irreversibly ban them though

Do you have a source for that? The article only mentions them being throttled + the screenshot with the support engineer saying they seem to be breaking the ToS and asking them politely to move back into compliance.

[nicce]

Well, CF is just one service provider. There are bigger issues if they have already such a monopoly that their decisions kill projects worlwide.

[ziml77]

Where did you get that they were irreversibly banned? Or banned at all for that matter?

[codalan]

They didn't get banned. They got an email from CF support saying that they cannot cache TXT files and that they'd need to disable the proxy.

This does not mean banned.

[laundermaf]

EasyList is a txt file. If they can’t host it on CF, it means they can’t use CF for EasyList.

They didn’t ban the whole organization, but effectively told them to stop. I don’t see a difference.

[codalan]

To me, getting banned is when the provider locks out (or just deletes) your account and prevents you from using their service entirely.

CF didn't do this. They sent them an email telling them that what they were doing was a violation of their TOS and to cease doing it. They did not kill off their account. They still have the option to comply and continue with CF, which seems to be what they are going to do at the moment.

Hopefully, CF will grant them amnesty on this one. At the end of the day, an HTML file is just a text file, so I don't see why this would have even mattered to begin with.