Post

Our Small World is Getting Smaller Still

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

I had my first taste of international communication today thanks to Google Wave. David Alviz runs an excellent Spanish Google Wave site called WAVEsfera. He keeps up with the latest bots and gadgets, and writes very well. A while ago it might have been a small problem that his site is entirely in Spanish. Translation has been around for a while on the web now, but it involved taking note of the site and plugging it into Babelfish or something similar. Now I have translation built right into Chrome. when I visit WAVEsfera, it asks if I want it automatically translated. Similarly, I’ve subscribed to the site in Google Reader, and it translates the site for me too! So far so good, no reason not to subscribe to international sites any more!

Blue Marble

Then I got to thinking. I’m getting in touch with some of the people who have read First Waves, and realised that it’s the perfect chance to try Aunt-Rosie, one of the original bots released with Wave. So I fired up a wave and added WAVEsfera and the translation bot. I selected the destination language and started typing.

It was true magic.

My amazement at watching my words translated as I type is like that of a caveman witnessing fire. the experience is so novel and potentially life changing. Imagine a world where language is no longer a barrier for communicating with anyone. Think of the potential for learning!

I’m full of excitement for the world of tomorrow enabled by real-time communication and translation. We’re so close to realising the universal translator of Star Trek that I can almost taste it.

In a site note: Inspired by my discoveries, I’ve enabled instant translation to each of my posts. I know I’ve had visitors from Germany, Ireland, the USA, France, Spain, the Czech Republic and Turkey just today! If you want to read First Waves in your language, check out the “[Translate]” button beneath each post. If you’re an international reader, I’d love to hear from you! Please leave a comment, or wave me at nunn.joshua@googlewave.com and don’t forget to add aunt-rosie@appspot.com!

Edited image from http://www.flickr.com/photos/wwworks/ / CC BY 2.0

Post

Emaily Gets Waves Out of Wave

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

In yesterday’s open thread, I used Mr-Ray by wave.to to allow non-wavers to access a wave. Mr-Ray’s real purpose is to be an intermediary between Wavers and emailers. It does this by creating a simple wave interface when you add someone to a wave by their email address.

Well Mr-Ray wasn’t the first attempt to get Wave and Email to interoperate. A couple of Googlers used their “20% time” to create Emaily, a bot that behaves very similarly to Mr-Ray on the Wave side, but tackles the email side of things a little differently. When you add Emaily, it first creates an email address for you on its servers. Then when you add the address of a non-waver, it sends an email to that person with the details of your update and they can reply right from their email. I have to say, it creates a pretty seamless bridge between the two worlds from the email side. In Wave though, you get to see their entire email shoehorned into a wave, with “>” reply markers and signatures left in. For anything more than simple communication back and forth this could get messy.

Picture 1.png

The developers of Emaily have said they are planning to integrate Emaily even more into Wave by “rearchitecting Emaily into an application, which uses more of the internal Google services”. Hopefully this could be the beginning of actual built-in email capability in Wave that could speed the transition of more users from old technology to new.

Try it today. Add “emaily-wave@appspot.com” to a wave and send an email to a non-wave friend! Will extensions like Emaily and Mr-Ray help you transition to Wave any faster?

Post

It’s Easter. So Chill Out, Try Wave, Check out Mr-Ray and Say Hello!

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

In honour of a couple of Wave extensions that allow wave-to-email collaboration, I thought I’d try something light-hearted instead of my usual wordy post. Mr-Ray is a bot/gadget combo from wave.to, that lets you add people to a wave by their email address, and they get sent a stripped back version of the wave that they can use to collaborate with you, without having to figure out and navigate the full-blown Wave interface. Embedded below is an example of the interface the email user sees. Please note, this isn’t the way the developers recommend using Mr-Ray — the address should be kept secret to avoid people posing as you. In this case, I KNOW it’s not me!

I’ve got a short holiday thanks to Easter, so I’ll leave this up until Wednesday to get to know my readers and give the non-wavers a chance to see a little bit how it works. I’ll check back regularly to reply so you come back too! If you’re already on wave and want to reply as you, contact me at nunn.joshua@googlewave.com and I’ll add you directly.
Read More »

Post

Six Things Wave Needs Soon

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

I love the potential of Google Wave, but that doesn’t mean I’m not sometimes frustrated with it. Here’s my list of stuff I’d like to see sooner rather than later.

  1. A way to “subscribe” to people/searches: Lisa Miller writes Our Patch (the First Wavezine) on Google Wave [“our patch” wave search]. John Blossom write useful waves about Wave [wave search for John Blossom]. I’d like to “subscribe” to these searches and have them tell me when new items are published by these people. The presence of “archive” and “mark as read” options when you make a search suggests it should eventually tell you when the search has updated, but it’s not implemented yet. Instead, users are making their own indexes (for example - Our Patch) And while we’re on searches — a “quick add” option to turn a search into a shortcut.
  2. Spam and abuse management: Spam and destruction seem out of control sometimes on wave. We know the team are building spam and user management, but it’s a bit slow going at the moment.
  3. Federation: At time of writing, federation (connecting one Wave server to another) is only supported in the developer sandbox and not in the public wave preview. It’d be nice to know that when Novell Pulse is released, they’ll both talk from day one.
  4. Moderation tools: Creators should have the choice to lock their initial blip from editing if that is what they desire. Some blips are purely informative and don’t need to be edited by all and sundry. This is perhaps antithetical to the way the creators intended Wave to be used, but users will do as they want with a tool, and it’s up to developers to support them.
  5. Google Apps support for all users: I don’t like using nunn.joshua@googlewave.com. I’d much rather use josh@nunnone.com as I have with email for the last 5 years.
  6. Better contact management: Currently contacts appear in Google Contacts under their Google email addresses. Why not add their names automatically, put them in a “Wave” group, and add a link to their home page pulled from their Google Profile (and don’t try to tell me Google doesn’t know that much about them…)

Coming Soon!

So that’s my list of “missing features” that are necessary ASAP. What do you think Wave is missing right now?

Image by http://www.flickr.com/photos/ilovememphis/ / CC BY-ND 2.0

Post

Why Email Needs Replacing (or Why Wave Matters)

In Post on 2010-03-30 by Joshua Tagged: , , ,

wave-email.jpg

It’s Old

Why it’s bad:

Email was invented 40 years ago to deal with a very different set of communication problems. The web didn’t exist, and email was a simple way to get text from one place to another. Think black screens with green writing and geeks talking to geeks across America. Now we have Twitter, Facebook, and whole new ways to communicate, but our basic building block is email. Everything useful eventually finds an implementation in email, but it’s ill-suited for the task. Sure it’s universal, but just sending images was an afterthought!

How Google Wave can help:

It’s built on the latest proven internet technologies. It’s built from the ground up to handle rich media of all different types but still retains some of the things that worked for email in the beginning, like addresses using the @ symbol to send messages to the right place.

Read More »

Post

How Wave Could Tackle the Spam Problem

In Post on 2010-03-30 by Joshua Tagged: , , ,

The Wave team have said very little about how they will address the spam problem, but from some clues and hints in the interface and what they have said, I can take a couple of guesses about how they could start to tackle it.
  1. First up, Wave will ensure messages are signed and verified from the source. Currently email can be forged and made to look like a legitimate email coming from a trusted source. The Wave Protocol specifically addresses this, making it impossible for anyone to “spoof” another address without access to that user’s account.
  2. Email currently makes it very easy to send millions of messages with little to no cost involved for the sender — they send and delete and don’t need to save copies of them, and the recipient is forced to deal with the accumulated data. The Wave Protocol however, requires the sender to host the wave and keep a copy for future reference. Spammers will no doubt find ways to send and then remove their waves, but if a host no longer hosts the wave, that could be a reliable indication that the sender was a spammer.
  3. Finally, the few times the developers have been asked about spam they’ve mentioned a possible white-list system. White-listing involves choosing who can send you messages and blocking everyone else. People worry that this will stop legitimate communication, say from long lost friends, getting through. But already built into the interface is a “Requests” link that Wave says are “Waves for users not in your contacts list”. This could allow anyone to contact you, but you’d know at a glance that they weren’t from people you knew and trusted, and could more easily add them to your contacts, or mark them as spam.

I believe a combination of these three factors will go some way to addressing the spam problem. By tying everyone to a Wave server it’s not as economical to spam using waves. By not allowing completely anonymous communication, reported spammers can be more easily shut down, and by white-listing users we can identify potential spam at a snap. The Wave team will hopefully come up with even more solutions to implement and I’ll be interested to see how it develops.

t

A quote from Novell: Demonstrating Inter-company Collaboration

The Google Wave Federation Protocol excited us, because for the first time since email, it provided a way for collaboration systems to cooperate in a non silo’d way . The promise is that each organization can choose what product to use and the communication will flow unimpeded between the different systems, in the same way that people on different email systems can send and receive messages to each other today. This is a collaboration revolution we wanted to be a part of.
“Novell Pulse and Google Wave” — Google Wave Developer Blog.

This is exciting. More detail up soon.

Posted 2010-03-26 by Joshua

Post

Google Wave Available to 31000 University Students

In Post on 2010-03-20 by Joshua Tagged: , , , ,

liu.gif

In a short and succinct tweet by Joakim Nejdeby, we finally have news of Google Wave in an Apps environment. With almost little to no fanfare.

Google Wave activated for our students, http://wave.student.liu.se #googlewave #Google #GoogleApps #liu
Joakim Nejdeby on Twitter.

Read More »

Post

French, Postboxes and Wave

In Post on 2010-03-18 by Joshua Tagged: , , , ,

When I was in grade 8 I learnt French. I say learn, but it was a handful of disconnected words and maybe a sentence or two that I couldn’t possibly remember now. The problem for me was that I knew I was going about learning it the wrong way, but relied on the teacher to teach me the “best way”. See, when I wanted to say a word in French, I first had to think of the word in English, then check my mental filing system for the equivalent word in French. It’s a slow and cumbersome way of recall that never really worked for me, no matter how many times we repeated the words by rote.

élégance by héctor*

I’m not bringing it up now to point out the flaws in my year 8 education, but to highlight something about the way people learn. When Wave was first announced and launched it was described by various people as “sort of like email” or “part instant messenger, part Google Docs”. This is because we often find it easier to understand something new when we “pin” it on a concept we already know and understand. Likening one thing to something else is sort of like my metal filing cabinet I had in 8th grade, useful up to a point, but no way to go about using something on an advanced day-to-day basis.

Which is why I think Google or a third party need to seriously consider how the non-tech-minded are going to learn how to use Wave.

Read More »

Post

First Waves — Focus and Feedback

In Post on 2010-03-16 by Joshua

waveblue.png

As a follow on from my last post, I felt the need to clarify that this site, First Waves, is not meant to be cutting edge day-to-day technology news. As Google Wave slow cooks over time, so will the posts here. I will cover important developments as they happen, focusing on the shaping of the Wave interface and the maturing of the Wave Protocol.

I want to make it easy for my readers to keep up-to-date as Wave grows, so I’ve added some social media gadgets over in the sidebar. If you join up in some form, I can let you know when First Waves has new content. I’ll refine and make some decisions about which ones I keep in future, so if you have a preferred method, sign up with it now to help me decide which ones to keep! I also have a feed to subscribe to (which also provides an email option) and I update the First Waves Twitter account with posts from here. As you can see on the side there, FirstWaves follows a few hand-picked Wave Geniuses which you can follow with one click if you want to.

I’d love for input and extra perspectives on Wave from the wave community too if you’d like to contribute. You can suggest posts using the Skribit tab in the top left, or email me at josh@firstwaves if you’d like to see something of yours in print.

I know it’s a bit backwards to use a blog for this instead of a Wave, but as the tools that are built for Wave improve, I’ll hopefully do some sort of crossover/merging to cater to dedicated wavers in their native environment!

Let me know what you think in the comments below.