First impressions / predictions on Google Wave, Google’s new communication idea/product/protocol/service:
- because it’s open-source, federated, and follows the same trust patterns as email, it will be successful
- whatever authentication protocol Google Wave uses will be a significant (if not a crushing) player in the web authentication space, and that’s not a bad thing because it looks like identifiers are email addresses (I’ve made this point before.)
- the brains of our kids are going to be very differently wired once they learn to use this kind of instant, multi-threaded, collaborative communication. I know I’m going to have a hard time getting used to it, and I can’t imagine my parents dealing with it.
Some questions and further thoughts:
- Are waves going to have permanent URLs? I hope so. Right now it looks like domain + wave ID, which could be made (maybe already has been made) into a URL with a new wave: protocol. I hope they do a standardized mapping of sorts to http: URLs.
- Will the authentication protocol allow for direct, unmediated authentication between me and a web service, so that my Wave server doesn’t need to take part in every login I do online? That would be nice for privacy.