Re:What we built with Twitter that now won't fly
by voyou on Friday August 17, 2012 @07:50PM
(#4399478)
Is that really incompatible with the Twitter display rules? The only things I can see on the News page that don't comply is not displaying the user's avatar and not displaying reply, retweet, etc., links. It seems like both of those could be added without cluttering the design too much.
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).
Re:What we built with Twitter that now won't fly
by jlewis_st on Friday August 17, 2012 @08:37PM
(#4399655)
Yeah, we'll do what we can to comply. If you're signed up and have your Twitter account connected you do get the reply/retweet functionality on hover. We like the calm of having no avatars, but we could add them (and see if we get busted if we let users toggle them).
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.
Re:What we built with Twitter that now won't fly
by hna0002 on Friday August 17, 2012 @05:22PM
(#4398874)
Good Stuff! From the demo, it looks more like a 'deck' to me. Is there going to be a handle for each user where other users can visit to look at? (That means always public?) How are the sharing relationships defined?
Re:What we built with Twitter that now won't fly
by state on Friday August 17, 2012 @05:28PM
(#4398909)
You can make specific workspaces public and follow other people's workspaces, but everything is private by default.
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'.
Re:What we built with Twitter that now won't fly
by state on Friday August 17, 2012 @03:57PM
(#4398446)
We'd like to build something that people find indispensable enough to pay for. How exactly that works: we're still thinking about it.
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.
Re:What we built with Twitter that now won't fly
by kamau on Friday August 17, 2012 @04:01PM
(#4398471)
I see. Yes Twitter can be unpredictable at times... At first glance I thought that were canned images and text; didn't realize they were just random people on Twitter.
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.