If you’ve been on vacation for the past week without your computer and cellphone, welcome back. Here’s what you missed: Everything! Yes, in seven little days, we’ve watched in amazement as Google the Giant Internet Gorilla with unlimited financial resources jumped off the 1,000 foot cliff without a parachute and then set about discovering how to land safely. Google jumped head first into social networking with a new product, Google Buzz, and decided to kick start the project using the age-old business trick of tying the new product to an old one, in this case their 175 million existing Gmail customers.
In the process of introducing Google Buzz, Google got almost everything wrong. Ironically, it’s the only new Google product that’s ever been introduced without the beta label. We’ll let you be the judge of whether Buzz is ready for prime time. Consider the following. There was the exposure of people’s most cherished Little Black Books to complete strangers. And cross-scripting security issues have been reported with the potential of exposing users’ Google credentials which in turn provides the key to the Google Checkout castle not to mention all of your most confidential emails. Then there were complaints that customer’s geolocation data was being compromised without user authorization. If that wasn’t enough on your plate for one week, Google now has to contend with a class action lawsuit and several government investigations into its Buzz business practices. Aside from that, did we mention Google Buzz is a huge hit!
If social networking is your thing, then you’re going to love Google Buzz. Think of it as FriendFeed on Steroids. Rich multimedia and location-based services on top of everything you always loved about IRC. And, if you have an Android 2.0+ phone, it gets even better with complete integration into Google Maps 2.0.
Unfortunately, everyone has been so busy with damage control and Google bashing that there’s been precious little time to actually explore the potential for Google Buzz in the social networking community. Our brief look at the product and its potential suggests that Google has another winner on its hands. It’s just too bad it wasn’t introduced in a manner similar to Google Wave so that users (and Google) could walk before attempting to fly. Here’s our first crack at how Google Buzz could actually be integrated into the blogging community, in our case making Google Buzz an integral part of a WordPress blog. And there’s also the widget approach from MoreTechTips.net which we’ve tweaked in the right margin below our Google maps. We’ll have more to say about these methodologies in coming weeks. In the meantime, come join the fun and Get Your Buzz On.
We’ve spent a week getting to know Google Wave using Chrome along with 100,000 of our closest friends. We wanted to give you a status report. Hype aside, Google Wave is an incredible tool when used for the right purpose. If you’ve been asleep or hiding under a rock for the past two weeks and missed the party, here’s a quick summary of Google’s latest invention. It’s a bird, it’s a plane… actually it’s a collaboration and communications platform that brings the full richness of Web 2.0 to your desktop. Some have suggested that it’s what email would look like if it were invented today. Our discussion focuses on the web-based Wave client, but Google Wave also is an open source development toolkit, and we’ll get to that one day soon.
Much has been written about Google Wave’s capabilities, and we won’t repeat that here. Instead, we want to address Google Wave’s potential and what we see as some of the present shortcomings of the product. We fully appreciate that this is a preview, and many of our concerns may yet be addressed before Google Wave becomes available to the general public. We can’t help chuckling at the realization that, in less than 30 years, we’ve now come full circle in data processing. What began as mainframe computing evolved into personal computing. And now Google Wave brings us much closer to being back where we started except for a state-of-the-art user interface and a new name: Cloud Computing. If IBM had addressed the user interface issues with mainframe computing, they probably never would have lost their market in the first place.
The screenshot above really can’t do justice to the richness of the client interface because you truly need a monitor as wide as your desk to get the most out of Google Wave. No, you won’t be using this on your cellphone or PDA… at least not well. For openers, Google Wave provides real-time collaboration so you actually see folks typing into various message threads (called waves) in the Land of Google. When you create a new wave, you “invite” other people in your Contacts to the wave. This puts the wave at the top of their Inbox in bold-faced type, akin to what Gmail would do with an incoming email.
There’s another frame to the right of your Inbox which actually displays the complete wave that you have selected so you’re never really jumping back and forth between selecting waves and reading them. What takes a bit of getting used to is the fact that both your Inbox and the wave you are currently reading may be changing every second with input from literally dozens of your associates or strangers if the wave you’re reading happened to be designated as public.
There’s one other dramatic difference in waves and threads of email messages. Other folks can change your stuff. As a collaboration tool with close associates, this might be desirable. With public waves, it would be a nightmare in the real world. And we don’t consider the 100,000 Google Wave previewers the real world. They are for the most part well-behaved probably out of fear that they’d be booted out if they behaved badly. That isn’t the real world as we all know. And the current Google Wave design would let a single creep destroy virtually every public wave in minutes using bots and malicious changes to documents. As presently designed, there would be little recourse other than replaying what your wave used to look like. You really can’t put Humpty back together again as some have already discovered.
Richard Nixon learned the hard way that tape recorders can be a blessing and a curse. Much has been made of the capability Google Wave offers to replay a wave so that you can playback the development of a thread of messages and see who added or deleted what and when. Google has touted the fact that everything is preserved. Well, not quite. First, there’s no capability at least presently to scroll back to a certain place in the timeline and recreate a new wave up to there. The most you can retrieve is a single posting. Second, anybody with access to the wave can use this timeline feature so wave restoration wouldn’t necessarily be desirable unless it were restricted to the original author of the wave. And, third, at least at Google someone knows how to cheat the system and delete stuff from the timeline. We only discovered this in reviewing the first public porn wave which started out prim and proper enough but quickly gathered steam when someone posted a collection of NSFW (or anywhere else) photos from their favorite collection. Within a few minutes, the postings quietly disappeared. Being the careful reviewer that we are, we immediately reached for the Playback button to check the history of the wave. Sure enough, the raunchy photos were still there. But, by the next morning, they had completely vanished from the chronology. So much for the official stance that nothing ever disappears. The real disappointment with the replay function is the lack of any capability to restore an entire wave. Because only individual messages (known as blips) can be recovered, this would prove to be next to worthless in a complex wave with hundreds of postings.
That brings us to the issue of whether public waves really make sense given the world in which we live. The good news is it works much better than IRC because of the richness of the content with attachments and hyperlinks. But, at least for public waves, the ability to edit someone else’s stuff would have to go. We try not to focus on legal nightmares in reviewing new software, but one can’t help wondering what would happen if one were to post something complimentary about a neighbor in a public wave and then another neighbor altered your posting by falsely accusing the individual of sleeping around with half of the neighborhood. Obviously, there’s still a good bit of work to do on the security front and in deciding whether allowing others to amend someone else’s postings is a good idea. Whether Google gets the security piece right will ultimately determine the success of Google Wave.
For public waves, it’s a no-brainer. You just can’t! And, to be honest, in reviewing hundreds of public waves in the preview, we can’t recall a single instance where this functionality would have been necessary. In a true (private) collaborative project, it would be wonderful but color-coding of text or some other method of identifying who wrote what would be absolutely essential from both a practical and legal standpoint. Both Microsoft Word and WordPerfect have had this capability forever. The simple way in Google Wave would be to add user’s pictures with a colored border and matching colored text whenever they make changes to someone else’s posting. With this addition, Google Wave could become a wonderful collaborative tool in both legal and technical environments.
And, speaking of word processing, Google Wave falls a bit short on the word processing scale. Despite the richness of Google’s knol platform, some of that functionality still is not available in Google Wave. The text editing and formatting is much akin to what’s available in a typical email client. You can change fonts, adjust color, indent, add hyperlinks and images, but that’s about as far as it goes. There are no headers, footers, footnotes, etc. So you can’t easily transform a wave into a formatted document for printing at this juncture. But that may come as development continues.
There are a few other things still on our Wish List. First, we’d love for Google Wave to evolve into a tool that can replace today’s forums which are not much more functional than BBS software was two decades ago. Once there is administrator control of rollback and protection of waves by granular access rights to functions, bots, and gadgets as well as the ability to block users and ranges of IP addresses, this should happen. Second, we obviously want the ability to include either read-only or read-write access to waves in a blog or web site. We already have the web site functionality working (see below for a sample), but you currently need a Google Wave account to access it. Third, we really want to assimilate all of the tools we use into the Google Wave Desktop so that everything is accessible in one place. That’s what Cloud Computing is all about, and Google Wave comes closer than anything else in meeting that need. You already can access Gmail on your Google Wave desktop and any web site that can be framed can be included in a wave as an iFrame. That doesn’t leave much once the security feature set is in place to protect all the components.
Finally, we’ll close with a brief mention of the coolest feature of Google Wave. That is its expandability which is enabled by incorporating bots and gadgets into any wave. As you might imagine, these extensions can do almost anything… good or bad. Here’s a short list of what has been developed and what’s already on the radar in just a few short weeks:
Chatbots Eliza – firstname.lastname@example.org – An implementation of the Eliza chatbot borrowed from the NLTK. Elize – email@example.com – Is one of the first robots that was created by non Googler and is very useful if you are feeling alone in your Google Wave client. Rude chatbot – firstname.lastname@example.org – An obnoxious chatbot borrowed from the Natural Language Processing Toolkit. TooAngel Wave – In Progress – email@example.com – A self learning robot, that will respond to a reply in a more humanoid way
Conversion BotURL – firstname.lastname@example.org – A URL Linker that replaces full URLs with hyperlinks. Calcbot – email@example.com – This bot will do in place calculations for simple mathematical expressions and allow you to use user defined variables. Cartoony – firstname.lastname@example.org – Replaces the text of every submitted blip with a cartoon balloon that contains the text instead. Colors the balloons based on username. Dice Bot – email@example.com – Dice-rolling bot. Dice Bot will replace XdY (X is the number of dice; Y is the number of sides) with the results of those rolls. Flippy – firstname.lastname@example.org – Turns text upside-down. Fnordlinky – email@example.com – Replaces “PMID <number>” with article information from PubMed. Hearty Emobot – firstname.lastname@example.org – Replaces ASCII art with wingding characters. i-cron – email@example.com – Evaluates Python expressions. Looks at blips in event, searches for CALC() macros and executes Python code using exec(). Insulty – firstname.lastname@example.org – Information Needed IPA Bot – email@example.com – Changes normal letters into special characters used for phonetics.
Games Hangman – firstname.lastname@example.org – Play Hangman.
Roshambo – email@example.com – Play Roshambo (Rock / Paper / Scissors).
Speedy – Wish – Track the words per minute of all participants, competitive typing!
Groups Groupy – firstname.lastname@example.org – Robot to manage groups.
Integration drop.io – email@example.com – Creates a drop and puts the info into the wave whenever the robot is added as a participant. OpenAustralia – In Progress – A robot to allow interaction with the OpenAustralia web site. PlonieBot – In Progress – firstname.lastname@example.org – Brings wave document editing capabilities to the Plone CMS Poppy – In Progress – email@example.com – Helps bridge Google Wave conversations to email users outside the Wave. Rssybot – firstname.lastname@example.org – Turn google wave into an RSS reader! Starify – email@example.com – Lets you star waves, in sort of bookmarking style. Tweety the Twitbot – firstname.lastname@example.org – You can access your Twitter account. Twiliobot – email@example.com – Transforms phone numbers into click-to-call links. If user clicks a link, a call is placed to his phone and to the number in the link. The call can be transcribed and inserted into the wave as text with a link to the audio. Wave-Email – In Progress – firstname.lastname@example.org – Provide an extension to Google Wave which will allow the integration of both sending and receiving emails. Wave Live Messenger – email@example.com – Allows you to chat to your windows live messenger contacts from inside a wave.
Language PhilBot – Wish – A suggested solution to the problem of waves with languages you can’t read. Rosy Etta – firstname.lastname@example.org – Translator (40 Languages).
Polling Polly the Pollster – email@example.com – Poll Bot.
Search / Aggregation Dr Maps – firstname.lastname@example.org – Updates a wave by inserting a map associated to an address. Dr Weather – email@example.com – Gives the weather for a City Embedded Search Results – firstname.lastname@example.org – Web and Image searches inline. FML Blipper – email@example.com – displays random FML story from www.fmylife.com Grauniady – firstname.lastname@example.org – Searches the latest items from The Guardian for a given phrase. Stocky – email@example.com – Detects stock symbols from a wave and updates it with the live stock price. Wavethingy – firstname.lastname@example.org – Searches Amazon for DVDs and books, and gives the author a cut of any purchases made off the links. Yelpy – email@example.com – Searches Yelp with a user defined location and category.
Utilities AmazonBot – firstname.lastname@example.org – Enables social product research and shopping on Amazon.com. Wave participants can share products & reviews with contacts in real-time thanks to automatic queries by the AmazonBot against conversation keywords. The AmazonBot gadget can detect products and return inline product links or a custom full product browser.
Bloggy – email@example.com – Information Needed Bit.ly Bot – firstname.lastname@example.org – Shortens the url using bitly. Botty – Wish – Will automatically add a set of useful bots to a wave according to a collection of bots (so they don’t have to individually be added when you use them all the time. CountColon – email@example.com – Adds text statistics to your blips (words, lines, etc.) Companion Sphere – firstname.lastname@example.org – Collection of geek utils, first working verb is “lookup” for wikipedia/wiktionary one-line descriptions. Databot – Wish – Will start as soon as the GData interface is published. Emoticony – email@example.com – Replaces text representations of emoticons with the relevant image. JBREAKOUT – firstname.lastname@example.org – Debug utility that reports event triggers. Maison – email@example.com – Makes blips public at http://maison.appspot.com. Multi – firstname.lastname@example.org – A quote collector. Reply a blip you want to quote with ‘quote this’ and randomly display a quote with ‘quote <wave @account.com>’. The bot is still being under development but you can try playing with it. Natural Language Processing – email@example.com – Adds blips with NLP analysis. Nokar – firstname.lastname@example.org – Has many features such as translations, image insertion, insert last tweets etc. Posterous – email@example.com – A robot for posterous.com user to post blog in Google Wave. Here is how to write a blog using Google Wave Robot for Posterous. Publisher – firstname.lastname@example.org – Information Needed Skimmy – email@example.com – Converts text emoticons, from : ) to img. Has a bookmarklet which creates a popup menu to insert emoticons for which the code is unknown. Smiley – firstname.lastname@example.org – Changes the smiley symbols to smiley images. Smiley – In Progress – email@example.com – Changes the smiley symbols to smiley images. Style Chart – firstname.lastname@example.org – Inserts a chart into a wave.
Wave Management Bouncy – email@example.com – Allows you to remove robots from a wave. Doesn’t seem to work on real people though, and laughs if you try to ask it to kick itself out. To get it to kick a bot out, type “bounce:firstname.lastname@example.org” Linear – Wish – Enforce all replies to be to the main wave. If a user replies to a reply, remove it and place it as a reply to the main wavelet. Read Onlie – email@example.com – Records the original wave content. Whenever it’s edited, the content is replaced with the original. Simple as that. Seekdroid – firstname.lastname@example.org – You can list Robots, add them and find them out, easy to use. In continuous development. Website with all the information seekdroid.appspot.com. Sweepy – email@example.com – Remove empty, whitespace-only blips. Taggy – firstname.lastname@example.org – Recognize #hashtags and add them as tags to the wave. Tocgen – email@example.com – Table of Contents auto-generated and updated based on the h1,h2,h3,h4 in a wave. Twitusernames – firstname.lastname@example.org – Replaces all Twitter @username with links to the Twitter accounts.
Gadget Utilities Ajax Animator – In Progress – http://antimatter15.com/ajaxanimator/wave/manifest.xml – A fully integrated multi-user web based vector graphic animation authoring environment. AmazonBot Gadgett – http://amazon-withwaves-com.appspot.com/gadgets/AmazonProductList.xml – The AmazonBot gadget can detect products and return inline product links or a custom full product browser. Bidder – http://wave-api.appspot.com/public/gadgets/bidder.xml – Simple Auction. Checky – http://wave-gadgets.appspot.com/checky.xml – Basecamp-like checklists with drag-and-drop.
Click me – http://wave-api.appspot.com/public/gadgets/hellowave.xml – Shows a button with a counter. Each time the button gets clicked, the counter is incremented by one. Shows off how the state interaction works. HTML – http://wave-ide.appspot.com/html.xml – Embed any HTML into a wave. iFrame – http://wave-ide.appspot.com/iframe.xml – Embed any web page into a wave. iWave – http://gadget.wave.to/iWave/iWave.xml – Allows you to create a profile on wave to make wave just a little more personal. Uses facebook connect to retrieve your details if you sign in. Licensing – In Progress – http://wave-license.appspot.com/license_gadget.xml – Creative Commons RDF Embedding – Planning Stage. Maps – http://hosting.gmodules.com/ig/gadgets/file/101415471413908368316/mappy.xml -Embed Google Map. Napkin – http://my-wave-gadgets.appspot.com/wave/NapkinGadget.xml – Example of Flash/Flex Wave Gadget, similar to Whiteboard gadget above – source on Google Code. QuakeBot – In Progress – Server information on the Quake 3 protocol. Raffly – http://raffly.googlecode.com/svn/trunk/sandbox/raffly-xml1/raffly.xml – Insert this gadget to select a random participant from your wave to be the winner. The winner of what? Well that’s up to you 🙂 Ratings – http://google-wave-resources.googlecode.com/svn/trunk/samples/extensions/gadgets/ratings/ratings.xml – Lets participants rate and review a topic (movie, restaurant, etc) in a wave and shows a tally of the result. Slashdot Gadget – http://www.m1cr0sux0r.com/slashdot.xml – Loads latest Headlines from Slashdot. Troco – An experimental peer-to-peer currency – http://troco.ourproject.org/gadget/org.ourproject.troco.client.TrocoWaveGadget.gadget.xml – Aims to provide a decentralized complementary community currency system, that is, a peer-to-peer currency system. Also you can see it as an IOU or promissory note based system. More info click here. Vector Editor – http://jsvectoreditor.googlecode.com/svn/trunk/wave/vectoreditor.xml – A cross platform collaborative real time vector graphics editor. Whiteboard – http://vps.michaelrose.id.au/canvas.xml – Draw on a virtual whiteboard. Who is Coming? – http://wave-api.appspot.com/public/gadgets/areyouin/gadget.xml -Show a list of all people that have said whether they will come or not.
Gadget Games Backgammon – Wish – Remove all of one’s own checkers from the board before one’s opponent can do the same. [Wikipedia] Battleship – Wish – Displays different board based on user. Boxes – In Progress – Connect lines to make boxes and win. Connect 4/Four-in-a-row – In Progress – email@example.com – http://www.sdunster.com/wave/four.xml – 2 users + observers, turn locking, just waiting to write win-detection code. Floodit – http://gadget.wave.to/floodit/game.xml – 2 player race to fill a board with colors. Magnetic Poetry – http://hosting.gmodules.com/ig/gadgets/file/107558585548952247431/fridge-11.xml – Re-arrange random words to form poetry. Match them colors! – In Progress – Match 3 / gem matching game. Othello – Wish – Play Reversi. Sudoku – http://blah.appspot.com/wave/sudoku/sudoku.xml – Play Sudoku. The Button – http://hyperthese.net/wave-gadgets/the-button.xml – A useless (I mean USELESS) game.
Hooks CVS integration – Wish – CVS history can be converted into a wave with playback. GIT integration – Wish – GIT history can be imported and played back (dffs). SVN integration – Wish – SVN History can be converted into a wave with playback.
Appearance Google Wave Scrollbars – http://www.uniformedopinion.com/google-wave-native-scrollbars-extension/google-wave.crx – Changes the wave scrollbars to the default system scrollbars.
Enhanced Google Maps. In case you haven’t noticed, we’ve added yet another Google Map to Nerd Vittles. Now, in addition to showing our location with Google Latitude, we also are displaying your location based upon your IP address. We’ll show you how to add something similar to any LAMP-based Linux system in coming weeks. It’s a powerful technology that has enormous potential. If you’re unfamiliar with Google Maps, click on the Hybrid and Satellite buttons and then check out the scaling and navigation options. Double-click to zoom. Incredible!
whos.amung.us If you’re wondering what your fellow man is reading on Nerd Vittles these days, wonder no more. Visit our new whos.amung.us statistical web site and check out what’s happening. It’s a terrific resource both for us and for you.
Awesome Vitelity Special. Vitelity has generously offered a terrific discount for Nerd Vittles readers. You now can get an almost half-price DID from our special Vitelity sign-up link. If you’re seeking the best flexibility in choosing an area code and phone number plus the lowest entry level pricing plus high quality calls, then Vitelity is the hands-down winner. Vitelity provides Tier A DID inbound service in over 3,000 rate centers throughout the US and Canada. When you use our special link to sign up, Nerd Vittles gets a few shekels down the road to support our open source development efforts while you get an incredible signup deal as well. The going rate for Vitelity’s DID service is $7.95 a month which includes up to 4,000 incoming minutes on two simultaneous channels with terminations priced at 1.45¢ per minute. Not any more! For our users, here’s a deal you can’t (and shouldn’t) refuse! Sign up now, and you can purchase a Tier A DID with unlimited incoming calls and four simultaneous channels for just $3.99 a month. To check availability of local numbers and tiers of service from Vitelity, click here. NOTE: You can only use the Nerd Vittles sign-up link to order your DIDs, or you won’t get the special pricing! Vitelity’s rate is just 1.44¢ per minute for outbound calls in the U.S. There is a $35 prepay when you sign up. This covers future usage. Any balance is refundable if you decide to discontinue service with Vitelity.
Some Recent Nerd Vittles Articles of Interest…
For those of you that already have Google Wave accounts, here’s a sample of how a wave will look in a WordPress posting. You can even add content to the wave! This works in Safari and Chrome most of the time, Firefox some of the time (if you turn on Accept 3d Party Cookies), and IE almost never. For those of you that are not part of the Google Wave preview, you’ll just have to wait patiently until Google turns on at least read-only access to this functionality: