Anyway, what happens when a developer community comes to life for a platform that's deeply nested inside a corporate silo? They can only communicate to the outside world through the constraints of the silo. But inside the silo, perhaps there's freedom! An Internet tries to boot up.
In early days of Twitter, like a lot of people, I was excited at the possibility of a centralized message router that we could all openly build apps on. But I also thought it would have been a good idea for Twitter to have an internal macro language, like Lotus 1-2-3 did, or dBASE or emacs, or Unix or really any good rich data or text environment. If Twitter was going to be the router, why not put some logic inside the router as well as around it.
I think the public folder of our Dropboxes has the potential to be an Internet-Inside-The-Internet as well.