Google Wave, meet your first troll

Over the past half hour - in a flurry of furious deleting, live-editing, dissappearing blips and random expletives - Google Wave met it's first fully-fledged (well, fledgling, really - more on that later) troll.

The attack seems to have ceased, but it wasn't easy to shut down. Wavers used a Google link (and Twitter) to alert the Wave team, but response was slow.

What is really interesting is... what happens now?

Up to this point the developers preview version of Google Wave has allowed open and live editing. Anyone can jump on any public wave, and edit or delete any part of it they like - including the Wave title and blips/comments from other wavers.

It's obvious this is not a feature that will follow GWave through to general release. Will the Wave team have to move more quickly to lock it down, now it's been so thoroughly abused?

Also, I'm picking (hoping) they'll put something in place quickly to report and/or temporarily disable active trolls; an enormous amount of good, collaborative information can be wiped out in seconds by a concerted attack.

So, who was it?

The troll was logged on as charanwilliams@googlewave.com. charanwilliams@gmail.com led to wavers locating a related website, run by a 12 year old boy from Chico, California. The website tells us his Uncle hosts his site and paid for the name registration. Won't he be proud?

Of course, someone else could well be using young 'Charans' identify for this unhappy stunt; I sincerely hope not.


Post-publishing edit: we've since found out you can report a user for trolling, spam or other anti-social naughtiness by clicking on their avatar on the Wave you are in and dragging it to the 'spam' button. Easy!

 


This posterous was posted from inside Googe Wave.

Dipping my toe into the (Google) Wave...

A few first impressions from a very new Waver...

It's a big idea and it might just work. It's going to take a lot of people to reach that tipping point of universal usefullness, and they're all going to have to want to learn a new way to communicate online. Still, they said that about email once. And if anyone can...

I've found it hard to find people. Some people have found it hard to find me. Searching for wavers seems impossible unless you know their exact Google wave address, which is a little limiting.

You can't tell who is online. Apparently you could, but this function a dead duck right now. It needs to work.

I'll need to do things differently. Usually it goes likes this; I type like a mad thing then I read it, edit out half of it, swap the rest around, edit again, read one more time for tone/context/grammar... and then publish. Twitter meshes perfectly with this workflow. 

On Wave the live typing interrupts my flow, making me think before I type, making me more stilted (and less clever-sounding?) than I'd like. Also, wavers can see how truly bad my spelling is (I know, get over it). 

And frankly, I don't want to see all your editing either... I was happy thinking those gems sprang perfectly formed from your blindingly brilliant mind.

There are no girls here. Or I'm just not looking in the right place. Don't get me wrong, you lads are fun and all. But there must be some more Woman Wavers out there... and more kiwis generally.

Look me up if you like: kirsty.hughes@googlewave.com

(as an aside, it's surprisingly tricky to write about Wave without excessive bandying of naff wave-related phrases like toe dipping and riding the crest and diving into and all)

Googlewavebig

Constructing your comms strategy; it starts with great questions

I like this updated take on 'First Ask The Important Questions' method
of formulating a communications strategy (from the Frank Vizeum blog).

The questions are phrased in ways that may encourage even the most
reticent client to think/expand:

"Who are your biggest fans?"
"What makes them smile?"
"What are the hot issues right now?" and "When and where might be the
most potent moment to tell your story?"

I'd add "How will you measure your success?" to the list.

Read the full list on Frank Vizeum's blog.