Quantcast

Mozilla Raindrop and Google Wave Totally Unrelated

by rahsheen Mozilla Raindrop and Google Wave Totally Unrelated

First, everyone was waiting with baited breath for Google to release Wave. Google Wave was supposed to be the solution for all of our messaging and social media needs. It would replace FriendFeed, email, Twitter, Facebook, shrink Kanye’s ego, and solve world hunger. Once those few elite who got invites started to use it, we all realized it was no such solution. It’s a collaborative communication protocol and is not very well suited to replace your favorite social network just yet. It’s not even suitable to replace you email. Some might even go so far as to say it’s a solution looking for a problem, which would explain the many posts floating around about use cases for Google Wave.

google-wave

Now, Mozilla announces the release of Raindrop. Let’s get something straight from jump: the two have just about nothing to do with each other except that they deal with communication and have names related to water. I’m not sure why everyone wants to mention them in the same breath. While Google Wave is a communications protocol, Mozilla Raindrop is actually a communications aggregator. It’s goal is two-fold:

  1. To aggregate all of your messages from across all of your inboxes on various services in one place
  2. To organize those messages in such a way that that email from Mom is given higher priority than your umpteenth invitation to play Mafia Wars

3996189794_6870de5db4_o

Currently, you need an invite to get into Google Wave and you access it via your browser. To get into Mozilla Raindrop, you have to download it, compile it, and run it on your own system. You still access it via the browser, but it’s really more of an application than a 3rd part service. Your stuff is all stored on your own computer.

To review, comparing Google Wave directly to Mozilla Raindrop is like comparing a single book (Wave) to an entire library (Raindrop). Both projects are still young, though. I’m quite positive that they will mature and converge in some way. For instance, Raindrop developers could create a module that pulls in updates to your Waves. The Google Wave team could create modules to import your social activity and email accounts (although, Wave’s interface might make this difficult to deal with).

Either way it goes, I’m hoping these projects and others like them will help to change the way we message each other online. Email and inboxes in general are inefficient and annoying to deal with. How long have you had those hundreds of emails just sitting in there because you don’t feel like dealing with them? Between Wave and Raindrop, maybe we will start seeing our inboxes work for us instead of against us.

Category: Getting Things Done, web 2.0 | Tags: , , ,
  • Joshanderson
    I suggest http://www.showdocument.com - good app for uploading documents and
    web meeting, web based and free of charge. - josh
  • Joshanderson
    I suggest http://www.showdocument.com - good app for uploading documents and
    web meeting, web based and free of charge. - josh
  • Interesting article. Like you stated, Raindrop has nearly nothing to do with Wave. I'm just wondering where you got that the Wave testers don't know what to do with it? Have you tested it yourself? I'm on a few public Waves that have polls about whether testers find it useful (that is, people who really tried it more than 1 day in a row). To the question "Do you think that Google Wave will be really useful to you any time soon? " posted in ContentWave (googlewave.com!w+q7l0bBbyA), 42 answered "Yes", 1 "No" and 10 "Maybe". I think that's a positive result :-)

    Wave is surely not ready for everybody (and for professional use for sure), but it's such a huge change that it needs time to mature. Wave is a new protocol, which changes a lot of things in our way to communicate, it's not a dashboard which supports 10 protocols.
  • Said differently, I would say
    * Mozilla Raindrop's goal seems to _organize_ the profusion of protocols/networks/tools that already exist, but you still have to sign up for a Facebook account, a Twitter account, a YASN account and other tools if you want to use Raindrop's functionalities to the fullest. It's still a mess, just more organized. Raindrop may be open-source, but what happens behind the scene of each YASN is probably proprietary still.
    * Google Wave's goal is to _replace_ the profusion of protocols/networks/tools with one protocol, which is open-source, publicly documented and federated, and allows for many uses. In Google Wave, you can share your pictures and videos as you would with Facebook, you can organize meeting, you can write collaborative documentation, you can simply communicate as you would with email (except it's much easier for a new participant to understand what's happening there), you can chat, and many other things. The fact that people are still wondering what to do with does not mean that nothing can be done with it, rather that the amount of things that can be done is huge, and will lead to many innovations.
blog comments powered by Disqus
advertisement

Want It

Who's Talking

Powered by Disqus

The Goods

How-To's

Ex-Factor

advertisement