[tomudding]

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.

[pseudosavant]

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?

[pwinnski]

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

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

[pseudosavant]

Exactly, but only via a repo.

[pwinnski]

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?

[pseudosavant]

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.