It's actually 140 bytes, not characters, except when it isn't: http://groups.google.com/group/twitter-development-talk/brow...
Even after fixing their db/cache/queue infrastructure to not fall over in normal use, they still can't handle a DoS attack at all! They peer exclusively with the highest-latency and least-connected Tier1: NTT/Verio (incidentally, so do fellow idiots OpenDNS).
The business side is in fantasyland, as shown in the documents leaked to TechCrunch. Evan Williams has no idea what he's doing -- Blogger was pure dumb luck, it had already effectively died when it was bought and resurrected by Google.
I don't know how Alex Payne keeps himself sane in that kindergarten.
Call it "blatant incompetence" if you like, but I'm guessing you've written a buggy validation or regex once or twice in your life.
Escaping, damnit.
http://apple.slashdot.org/article.pl?sid=01/11/04/0412209...
They had a shell script which didn't "quote" their $variables. It rm -rf'd entire drives by mistake. It's why I use "$@" now.
The programmer responsible should be made to write out lines or something - "I must always validate every single user input".
Compared to the whole mikey fiasco, where he found a hole in the on display script for tweets.
I've responsibly reported my fair share of Twitter vulns over the years. In general Twitter fixed them quickly. (Except some CSRF/XSRF issue which was non-trivial and was when they had fewer resources.)
Dave Naylor was just irresponsibly publicizing something, which makes him somewhat of a jerk. Being a jerk is not necessarily a Bad Thing and of course we/I don't know the entire story here, but that's what it sounds like.