Wave Defacement

I just found my first case of wave defacement!

I was innocently perusing the public wave about votely (an extension which I plan to review soon), and I clicked on the link. Instead of the expected list of top public waves i expected, I was greeted by some really nasty porn.. . (don’t worry, i do not plan to review it).

I then realized that the link had been changed (I have used it before, and my first theory was that the destination site had been hacked).

I changed the link back to what it should be, and remembered the playback function, which I had not had reason to use yet, and I tracked back to see who the culprit of this dastardly deed was! It took me a bit of scrolling back and forth, but eventually I managed to identify when the link changed (as well as another changed link I had missed).

Soon after I announced my findings in the thread, the person who did that apologized, saying he had been upset with the person who started the wave, and changed it in anger.

So, everything was Ok in the end… But this incident did serve to illustrate a problem with the wave as it currently stands: The fact that anyone can edit a public wave… And in the cases of links, the editing need not be obvious to the casual glance. Like so many other people, I think Wave really needs some moderation capabilities.

Ironically enough, I had already been brainstorming a post about Google Wave Etiquette, so expect it sometime next week.

No TweetBacks yet. (Be the first to Tweet this post)
  • Share/Bookmark

Related posts:

  1. Wave Etiquette
  2. Google Wave Keyboard Shortcuts
You can leave a response, or trackback from your own site.

Leave a Reply

Comments links could be nofollow free.

Subscribe to RSS Feed Follow me on Twitter!