I don't understand how Semgrep decided to botch itself like this. A fork was bound to happen. Why would users continue using a project that decides it should now hide information for commercial purposes?
You are right I should do something rather than just complaining. Maybe somebody (or me) could do a patch that allows YYYY-MM-DD dates with dashes. Or YYYY-MM to specify a month.
http://en.wikipedia.org/wiki/ISO_8601
Very interesting visualization. It's always hard to wrap in mind what a Brainfuck program does while executing.
While reading the source of the interpreter, I found out that the "[" command is not working properly. It is suppose to jump to the next matching bracket when the value of the current pointer is zero. I'm quite sure the creator is aware of that as he wrote on the demo page what it supposed to do. Good work still !
Possibilities mentioned so far:
(1) Fame for attacker
(2) Excuse for other problems at GitHub
(3) Competitors
Not sure I find any of these is more convincing than the next or very convincing at all.
GitHub seems to be one of the least offensive businesses around but still gets attacked on a regularly. It's popularity might make it a target but don't those running botnets have better targets? And wouldn't they publicize their exploits?
And I can't believe GitHub would use it as an excuse. A DDoS attack has clear evidence that their entire devops team and many of their suppliers would have first hand knowledge of. If word leaked out it would be pretty embarrassing.
Lastly would a competitor risk destroying their entire business if found out. People are irrational and stupid but that would be crazy.
Is it really acceptable to include other peoples work that have a different license into the main file without any mention the original mention (only a link)?
As if it was licensed with GPL v3 to the author of Fly.js...
I just noticed that. Currently, if you use Fly.js in a project, as you give the source file to the custommer, you must use GNU/GPL license too, as explained here : http://stuck-in-windows.blogspot.fr/2009/02/fud-over-javascr...
I think I'm going to change the license.
Thank you for noticing it.