Poe's law is in action here, so I am not sure if you're serious. In case you are, you were not blacklisted for abuse, but the service you were using (the JSON editor) was blacklisted for abuse by the service that was hosting it (rawgit.com)
I've seen attempts at it before. It gets pretty complicated, because of attribute/content split. You're basically choosing between something so generic and complicated it's hardly any better than a validating text editor with autocomplete, or something so cut down that it is by default specialized to its use case, in which case it is basically just a specialized editor of some sort that happens to serialize to XML, which is common, and no longer is a "general XML editor".
I guess rawgit should change its strategy: they instruct people to not link to rawgit.com but to cdn.rawgit.com when you expect heavy traffic. The thing is that you have to read their instructions, which is probably not what you see when you receive a link to them. So you share that very same link, and if you share it on HN it crosses their threshold. Maybe they could use a redirect to their cdn URLs when such threshold is crossed, reverting it when some time is passed.
Beside, the redirect or a gentle message would be cheaper than serving evil.js and evil.css.
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.
When you have to put in a loop that crashes your users' browsers to stop them from "abusing" your free service -- perhaps you are doing something wrong.
Besides, what if somebody doesn't know his traffic is going to increase? It's not exactly something you can always predict. Just crash everyone's browser -- that'll show 'em!
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.
URL debacle aside, I think this seems like a pretty good tool. My only qualm is that it seems a bit busy. In my mind, a good json editor will make it easier to edit the data, but here I had to scroll more and click more.
I'm currently working on integrating this in my app. I really like the combination of json-schema and json as a protocol. Where no custom UI is defined json-editor jumps in to save the day.
36 comments
[ 1007 ms ] story [ 160 ms ] threadA working demo (although also on rawgit): http://rawgit.com/jdorn/json-editor/master/examples/css_inte...
http://cdn.rawgit.com/jdorn/json-editor/master/demo.html
Beside, the redirect or a gentle message would be cheaper than serving evil.js and evil.css.
I'm not sure i like this service anymore if this is their response to high traffic loads.
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...
Your medium article makes you look like even more of an asshole.
I'd be happy to provide a full refund if you'll come out from behind that cowardly anonymous throwaway account.
Besides, what if somebody doesn't know his traffic is going to increase? It's not exactly something you can always predict. Just crash everyone's browser -- that'll show 'em!
Your comment makes you look like even more of an asshole.
Blacklisted for abuse
This request has been blacklisted for abusing rawgit.com.
http://www.alpacajs.org/index.html
http://jsoneditoronline.org/
No thanks, with my data - its offline and safe, or not at all.