Take a look at what you need to pass to post a Twittergram; Twitter name, Twitter pass. Everything else, non-Twitter-specific and posting to your Twitter account is optional.
Imagine for a moment; Jaikugrams, Basecampgrams, Flickrgrams, Plazesgrams, Linkedingrams, and AnyServiceWithAnAPI-gram. The same exact Twittergram functionality riding atop each respective service 1.
Little birds flitting from rhino to rhino.
Ququoo.com has the same core functionality as another, much larger project I’m working on. Plus, I don’t need to write a login/pass registration system. In fact, that’s the rule w/ Ququoo development. It can’t have anything specific to Ququoo in it 2. Jen reminded me today of that. Her reminder has helped focus my Twittergram work – and dust off something this larger project needs desperately.
1. Number 3 if you’re following along.
2. Eric, maybe that’s the rule w/ Twitter as well
5 July 07 Update: Yes, I think Twittergrams can be any kind of file and be larger than 200k. Maybe not with Dave’s service. But once you and programmatically decode a tinyurl you’ve got the idea.
8 July 07 Update: Feels like this accomplishes the same goal as OpenID…from a different angle. Where new sites ride atop older more established sites’ accounts – this solves 2 problems for new sites; needing to develop an account creation system and getting people to use the service. Scaling means supporting one more pre-existing account system.