Post

Remove: Remove Yourself! Remove Others!

In Post on 2010-04-25 by Joshua Tagged: , ,

The most long-awaited feature (besides the seemingly dead “Draft” button) has finally been imlemented by the Google Wave team. That’s right, Remove Participant is here! What this means if you’re not an addicted Wave user, is that wave authors now have total control over who comes and goes from their waves.

remove-participant.png

This is a big deal for Google Wave. The button has been there since the beginning, but grayed out and unusable. It’s taken some of the shine off Wave that until today you were unable to recall waves or remove people added accidentally.

It works in a pretty straight forward way. You decide someone should not be a participant any more and you click remove. The person who is removed sees a big red X on the wave in their inbox and opening the wave shows the last thing they were able to see before you removed them. If you remove them before they even open the wave, they won’t even know it existed!

remove-from-wave-receiver.png

Part of me balks at the idea of removing waves right out from under their noses if they haven’t opened them. It feels somewhat dishonest — but it’s actually just fixing a email shortcoming! I think we’ve gotten so used to the idea that once something is sent, it can’t be unsent that it feels a bit weird to actually be able to do it again. Keep in mind though that this probably isn’t foolproof. If for example someone’s waves become “unsynchronised” while you are removing them from the wave, they might still see it — leaving you thinking that you got to it in time.

Another big issue in the months since launch has been Wave abuse. Waves have been destroyed by malicious (and accidental) addition of bots, or overwhelming the wave with large amounts of spammy text. At the moment, the best way to deal with this has been to reduce the abuser’s participation to “Read-Only” and report them to the abuse team. This remains the best way to halt an ongoing attack, but now it’s also possible to clean up after an abuser by removing the sign they were ever there in the first place.

  • Hey Josh, I followed your link from LifeHacker about your standup desk and you linked to this blog.

    I got in on Google Wave a while back now (I think it was the second big wave of invites) and did quite a bit of poking around and analysis of security measures and so on. In the end I decided that I probably wouldn't use Google's implementation of the Wave protocol due to the problem you mentioned at the end of this post: Wave abuse.

    I think that fundamentally the Wave protocol has a security "issue". Not a bug, not necessarily a flaw, but it has several things that make me uncomfortable with it. I wrote more about it on my research blag: http://www.tobiaslabs.com/59/some-security-issues-with-google-wave/

    I link to a support forum where a person argued that the "Remove" function of the Wave protocol may not even "make sense", but I think Google's implementation on this is pretty reasonable. I think I'll start using Google Wave again to see how I like the recent changes.
  • It really is a good time to get back into Wave. With Google I/O coming up, they're on a new feature spree at the moment, and it's only going to get better. There are probably a couple of posts I could write about why now is a great time to get back into Wave. The Wave Watchers (a group of wave enthusiasts and developers) are putting together a comprehensive post of this nature as we speak!

    As for your security concerns, I think it's right to be somewhat wary. It's new technology and a new idea, and it may very well have fundamental flaws in the way it's currently implemented. It is however, only a "preview" still, and anyone using it for top-secret sensitive data does so at their own risk. The way to minimise your risk is to not use gadgets that have not been thoroughly vetted (the source is always easily available) or not use them at all, and only invite users that you trust.
blog comments powered by Disqus