What we built with Twitter that now won't fly
office.sharingstate.com
office.sharingstate.com
Twitter's desire to micromanage how API users display content seems pretty stupid to me, but I'm not sure it will have the terrible effect on clients that people seem to think (the rules about not including third-party actions and not intermingling Twitter and non-Twitter content, however, are pretty obnoxious).
The part that is tough for us is third party actions. It's specifically those actions we're excited to enable. So while we don't anticipate having to totally remove Twitter data, we do expect it to become less useful and integrated.
It's unclear how draconian Twitter wants to be. We'll do our best to work with them while refining and adding other services as a hedge against getting cut out.
We like the idea that sharing happens around a specific set of content and we'd like to develop the collaboration potential further. As that happens the sharing relationships should hopefully go beyond 'following' or 'followed by'.
Not sure exactly what you mean by 'stack up', but they're all fairly comparable. Some are easier than others. We built a lightweight meta-API to deal with them all uniformly.
Serious note: Looks very interesting.