Re:Chris Messina's Thoughts on Opera Unite
by jimboyoungblood on Wednesday June 17, 2009 @01:52AM
(#661430)
Following this line of reasoning, Twitter is horrible because it doesn't adopt an open standard. Likewise Flickr. And delicious. And anything else with a homegrown REST API.
If their API is well documented, who cares that it wasn't designed and rubber stamped by a committee.
Re:Chris Messina's Thoughts on Opera Unite
by benburkert on Wednesday June 17, 2009 @02:15AM
(#661450)
Twitter has adopted open standards, they use oAuth. There's nothing wrong with home grown APIs, but I think APIs that ignore open standards will be a problem as services become increasingly interdependent.
Re:Chris Messina's Thoughts on Opera Unite
by factoryjoe on Wednesday June 17, 2009 @02:08AM
(#661442)
I think if Opera provided an explanation of how to set up a "Unite server" on your own server, than a lot of this controversy would be moot. That's why Google was so epic with their launch of Wave.
It's using XMPP vs. rolling your own chat protocol. Supporting oAuth for file access vs. a custom authentication API.
Everything I saw browsing through the docs is about how to develop for the unite platform. I don't see anything about interacting with a unite service outside of an opera browser.
In this sense, unite is a creative extension to an open standard, browsers with common functionality like firefox, ie, safari, etc.