Posts Tagged ‘editing’

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.

Post

Restore a Wave to a former state, or make it Read-Only.

In Post on 2010-01-23 by Joshua Tagged: , , ,

In the first major update to the Google Wave client in what feels like ages, the Wave team have implemented two new features that will make a big difference in managing your waves. The first fixes one of the most shocking things about the first release: that anyone you invited could come along and edit any part of your wave. Of course the point of Wave is collaboration, but sometimes it was conceivable that you might not like anyone to be able to hack away at a wave, particularly once a wave was made public. Many good useful waves were effectively destroyed by granting the public editing rights.

the read-only tool in action
Read More »

t

Add characters quickly to a wave

In Link on 2009-10-27 by Joshua Tagged: , , ,

Wave has a WYSIWYG interface for styling your blips. For those of us used to working on the web however, the default Bold/Italic/Dot-point tools can leave a lot to be desired. Many wont have a character pallet handy, or remember the windows/mac keyboard codes for producing various glyphs either. But if you’ve worked on the web long enough, you might be familiar with HTML/unicode character entities such as & (&) and •

If you need to add various characters to your waves, and are familiar with HTML entities, then the Character Entity bot might be what you need. Add character-entity@appspot.com to your wave, and whenever you write a character (in the format &code;) the bot will happily convert the code into the correct characters for you.

Here are a few to try:

  • © becomes ©
  • ↔ becomes ?
  • ∴ becomes ?

(A more detailed list can be found at Intuitive Systems)

Character Entity Bot [Google Code]