Chris Messina's Thoughts on Opera Unite
factoryjoe.com
factoryjoe.com
I like Opera, and wish them the best of luck with their business and their projects, but Unite doesn't change anything. It will be a barely used feature in a barely used browser.
Ever wanted to share all the photos/videos on your 120GB hard-drive? Unite does that too, bye-bye flickr.
Ever wanted to host online chat - it's already there in your browser now.
Ever wanted to listen to your music when all the files are on some other computer? Relay via Unite, it's in your browser.
Want to host web-pages on your local computer? Don't want to install a web-server .. no problem.
Really I find it awesome, I think we've only just scratched the surface here too. A genuinely new paradigm IMO, http://alicious.com/2009/opera-about-to-change-the-world/.
Welcome to the Peerweb.
Even ignoring the fact that the idea of "your computer" is becoming less and less a big box that sits on your desk and more and more a tiny device that you have in your pocket or your bag; and ignoring the fact that we'd really like for computers, even the big ones sitting on our desk, to sleep when not in use so we don't chew up so much power and produce so much waste; and forgetting about the fact that someone has to actually write the code for all of the magic functions to address the problems you've proposed Unite can solve (and for a proprietary platform that about 1% of users use); and discounting the chicken and egg problem that in order for this to be easily useful across all of your devices you have to have Opera on all of your devices. Even forgetting all of these, huge, probably insurmountable even to a company the size of Microsoft, problems, Opera Unite still doesn't solve any big problems that really effect users.
Yes that is one of the down falls, pretty major too, but if you're family wants to share from your computer they can just call, or you can look and see the connections are 0 before turning it off. I can also imagine a caching/on-line backup system (like Dropbox) - eg for your fridge notes.
Peerweb is not the www they have a lot of overlap but this is going to change the way we use computers IMO.
As far as "Welcome to the Peerweb." Wow, talk about drinking marketing Kool-Aid.
As far as a new paradigm is concerned .. not really. I think a new paradigm would be more like a rich technology that doesn't use the Web/HTML/HTTP at all.
As dumb as Opera is, they're not stupid enough to pay for all your live filesharing bandwidth, symmetrically.
And, that they used such confusing and contradictory terms in their EULA.
I understand that you were primarily criticizing/debunking the reason d'etre and social crap in the copypastad press-release -- not the technical handwaving.
What is your proposed solution?
AllPeers required an AllPeers client on both ends, right? But then you undermine the whole Unite concept, don't you?
One point that Chris didn't make in his post is that the problem they identified as the reason for building Unite (or so they say), the loss of ownership of one's data to third party services, is the same dilemma that inspired DiSo.
The reason DiSo is relevant, and unite is not, is because the good folks (like Chris) behind DiSo recognized that it's not just about where your data is stored. Just as important is that the format is open and interoperable. Although Unite has this quasi distributed model, it's formats/APIs are (AFAIK) unknown, not based on open formats, and for all intents and purposes, as good as proprietary at at this point.
Pushing the 3rd party into the browser is not a solution to the problem.
http://unite.opera.com/support/#services_tech http://dev.opera.com/articles/view/opera-unite-developer-pri...
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.
If their API is well documented, who cares that it wasn't designed and rubber stamped by a committee.