Actually, I've tried both approaches. Redirecting does nothing to reduce excessive traffic, because nobody notices they're doing anything wrong. The traffic just keeps coming, and I keep having to redirect it, which doesn't help me at all.
Displaying an annoying message, on the other hand, gets fast results, because _everyone_ notices and complains.
Both rawgit.com and cdn.rawgit.com are completely free (the former paid for out of my own pocket, the latter generously donated by MaxCDN). I don't think it's too much to ask that a person read the prominent instructions before using this free service.
No worries at all. I'm working on improving the messaging when a URL starts triggering abuse prevention measures to hopefully avoid confusing people so much.
Actually, I've tried both approaches. Redirecting does nothing to reduce excessive traffic, because nobody notices they're doing anything wrong. The traffic just keeps coming, and I keep having to redirect it, which doesn't help me at all.
Displaying an annoying message, on the other hand, gets fast results, because _everyone_ notices and complains.
Both rawgit.com and cdn.rawgit.com are completely free (the former paid for out of my own pocket, the latter generously donated by MaxCDN). I don't think it's too much to ask that a person read the prominent instructions before using this free service.
For more background on how rawgit's abuse prevention works, read this article I wrote about a particularly painful incident: https://medium.com/the-javascript-collection/the-naughtiness...