which is at least detected by https://downdetectorsdowndetectorsdowndetectorsdowndetector....

I really expected that one to be a joke

Good god, what have we done ...

This is now my favorite post on HN

Turtles!(Expletive!)

(2020)

Yes, fixed in all (at the time) supported versions in October last year [0].

[0]: https://github.com/php/php-src/commit/248f647

I have been using the Timeless skin [0] for quite some time now and the main reason I switched was that the content would be a bit more condensed towards the middle of the page. This helps a lot on larger monitors and I can see why this new theme also does something similar. However, the large amount of whitespace on the sides is just wasted and in combination with the fact that more interaction is required to do basic things (like changing the language of a page) is something that makes this new theme not "barely noticeable".

[0]: https://en.wikipedia.org/w/index.php?title=Main_Page&useskin...

There is a list of partners [0], I thought I had seen regexes at some point but I can no longer find them.

[0]: https://docs.github.com/en/enterprise-cloud@latest/code-secu...

He leaves behind a great legacy. I can highly recommend Blood Music, Eon, or Forge of God if you have never read one of his books. However, my personal favourite was actually the (Halo) Forerunner Saga series.

Cloudflare caches robots.txt by default when proxied (the only .txt-file that they automatically cache), for all other content the following from their ToS probably applies:

> 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 as part of a Paid Service or expressly allowed under our Supplemental Terms for a specific Service.

We will never know the reasoning of the support agent who replied to the EasyList maintainers, but I can imagine that it is indeed disproportionate for EasyList.

I really hope that Cloudflare actually sees that they are making a wrong decision here and actually help the EasyList maintainers.

The TOS isn't that you can't serve plain text, it's that it shouldn't be disproportionate in volume to the cached html served.

That could be solved by tacking on 2x the file size worth of pointless html code to the file.

What's the difficulty supposed to be? Serve the same thing with a different MIME type and you're in compliance.

GitHub has a soft limit of like 100 GB/month on transfers for Pages. According to the Adguard blog post traffic was already several TBs a day before the issue arose.

Why not only provide the list as a repo? You can't hotlink a repo. And someone abusing raw links is GitHub's bandwidth problem.

'Legitimate' users of the list would clone/pull the repo to their own mirror?

Do you mean like this? https://github.com/easylist/easylist

EasyList updates frequently, many times each day, as the commits to that repo demonstrate.

Exactly, but only via a repo.

I'm curious, if an arbitrary GitHub repo suddenly started attracting hundreds of terabytes of egress, violating GitHub's ToS, would GitHub manage traffic in coordination with the repo's owner, or would they disable the repo and suspend the account?

I suspect the latter. I don't know how to make a repo public but limit web traffic to it. Do you?

I could see disabling viewing raw links. But if the repo becomes popular to fork what would GH do? The friction of using git instead of HTTP will prevent 99.9% of hotlinking. So it probably couldn’t become too popular.

> but want to make sure we do it right.

Make sure you do it differently than how Muse Group did it with Audacity (specifically the announcement and explanation of why and what parts) [0]. Which I'd argue is not particularly difficult to do.

[0]: https://arstechnica.com/gadgets/2021/07/no-open-source-audac...

Previous discussion here:

https://news.ycombinator.com/item?id=30499150