Why Google Wave Sucks, And Why You Will Use It Anyway
via techcrunch.com
Explore Posterous
Search posterous
Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
More posterous blogs
Here are posterous posts filed under googlewave...
Google Wave: 15 features
via youtube.com
A simple overview of how to use Google Wave.
Google goes blue
Okay, so Google has made quite a radical change to it's iconic startpage interface. Go to google.com (it has to be the english version) and type in the following in the url field:
javascript:void(document.cookie="PREF=ID=20b6e4c2f44943bb:U=4bf292d46faad806:TM=1249677602:LM=1257919388:S=odm0Ys-53ZueXfZG;path=/; domain=.google.com");
Hit enter, then visit google.com again. You see it? It kind of looks like Google Wave if you've had the chance to try it out.
I'm sure Google has lots and lots of talented designers in their team, but to limit their talent and experience to this - and this is probably the most radical redesign they've done in half a decade - is such a waste. It actually looks like an early mockup for a web site. Exactly like Google Wave does. I hope this doesn't influence the industry and it's designers that much.
Play around with Google's cool new interface
via pocket-lint.com
Google is currently experimenting with its monolithic homepage to make is just that little bit more useful for the likes of you and I.
Not only does it look a little bit cooler with the "Chrome/Wave blue" it has begun to use elsewhere, but the search interface is more consistent. Users will be able to flip between different types of search result using the toolbar on the left of the screen (see above), which is especially useful for any kind of marketing research or cyber stalking. All results are delivered in a clean and consistent style.
To play around:
Visit Google.com (not .co.uk or any other regional site), log out of your Google account if you have one and paste the following into the address bar:
javascript:void(document.cookie="PREF=ID=20b6e4c2f44943bb:U=4bf292d46faad806:TM=1249677602:LM=1257919388:S=odm0Ys-53ZueXfZG;path=/; domain=.google.com");
Der Google Wave Podcast
Podcast #16: Google Wave
Lang hat´s gedauert doch gestern Abend haben wir´s doch endlich hinter uns gebracht. Der schon vor längerer Zeit angekündigte Podcast mit Stefan Keuchel, dem Pressesprecher von Google Deutschland, über den neuen Echtzeitko
Mommy, what's Google Wave?
Found this interesting article that I would ordinarily excerpt and link to, but it's inside a massive Wave, which is in the process of crashing my browser. If you're on the wave, have more RAM than me, and wanna wade through the wake, surf here.
I remember the first e-mail I ever sent. It was to Bobby Chen, the elder brother of my darling high school friend, Susan. He was a year or two older than us and had just started his first semester at Stanford. I guess I was aware that people in college all had e-mail, and I had figured out how to use Prodigy to send messages to non-Prodigy recipients. I waited, breathlessly, to see if Bobby got my e-mail. Miracle of miracles, he did.
Speaking of Prodigy, where the eff are my old pioneer cyberdork friends from The Potpourri Lounge? There was a time when I would have seriously argued that, as fourteen year-olds, we started the internet. Certainly, we were among the first to experiment with placing things like <evil grins> and <Richie syndrome> between chevrons. But today, my Google search for <prodigy "potpourri lounge"> yielded two measly, inapposite results. Michael Locke? Grace Kang? Abra somebody? Who else? If you ever see this, please give me a shout. I don't know that I could have survived the crippling awkwardness of those years without you guys.
Anyway, I digress... .
§ § § § § § § § § § § § § § § §
The Second Web: What Google Wave Really Means
The first Web isn't dead. But long live the Second Web.
The first Web is without a doubt one of humankind's greatest inventions. Marrying easy-to-use graphical browsing of hyperlinked content on Web servers, simplified publishing tools and powerful search engines, the World Wide Web revolutionized our ability to communicate through electronic publishing with audiences of virtually any scale. Billions of people use the Web every day, and many of those people are in turn Web publishers themselves through the use of social media services and tools. How could we have it better than the Web?
Well, we could.
What the Web Never Did Well
One of the things that the first Web never really dealt with was email. It was a largely outdated technology when the Web was invented and in most ways it has become only worse as a communications medium, in spite of our daily reliance upon it.
The Web also never dealt very well with programming and editing content. This lead to the rise of additional and often proprietary technologies for supporting complex Web content displays. Web 2.0 publishing tools have improved our ability to publish and collaborate simply on the Web, but they fail to provide a unified and open standard that allows everyday people, enterprises and online publishers to edit and interact with content and people efficiently.
Finally, the Web was invented in an era in which the phrase "real-time" was applied mostly to things like stock quote feeds and scientific research. Today the Web supports real-time services such as Twitter messages, phone calls, videoconferencing and a wealth of mobile applications triggered by Web-supplied updates. The Web manages to deliver these services, but in truth it was never well-designed for real-time. Can you say, "Fail-whale?"
What The Second Web Does Better
As exemplified by the introduction of Google Wave, there is a better way to deal with the problems that the original Web never dealt with particularly well. Those better ways build on the strengths of Web technologies but are not limited by some of its inherent weaknesses. We can call these better ways The Second Web. Like a new car in the driveway sitting next to our "old reliable" car, The Second Web takes us many of the same places that the original Web has taken us, but with a new generation of technology and a new focus on its purpose.
What defines The Second Web? Looking at Google Wave and related Web technology and service developments, I believe that The Second Web incorporates a number of key attributes:
- The Second Web is conversational. At the heart of Google Wave is an open source protocol that is designed to support simultaneous two-way exchanges between groups of people - or, to put it more simply, conversations. The original Web was never designed to deal with conversations at all: it was simply a technology to make it easier to retrieve information stored remotely. Google Wave "documents" are often used as records of conversations - and, often enough, host multiple simultaneous conversations. The Second Web is not a place that you go get get content to use elsewhere. It's a place where content is born, grown and consumed all in one spot by groups of people, often in real-time. Once audio is integrated into The Second Web more efficiently, the full power of its ability to support conversations will become more clear.
- The Second Web is easy for anyone to edit and program. While tools such as blogging servers and social networking portals make it easy for people to create content online, once it's there, well, it's there, pretty much. The Second Web is based on the premise that any of its content could be edited and programmed by anyone as easily as writing an email, attaching a file or making a comment on a Web site. Just click, type, drag and drop - and it's there for the world to see and interact with. If you want to change a published document, go ahead - it's all the same method, whether it's just a note to your friend or a page for all the world to see. The Second Web will crash through publishing technology barriers and enable billions more people around the world to publish efficiently and effectively.
- The Second Web makes collaboration a default, not an exception. Unless you happen to be visiting a relative handful of Web sites that use (typically) techie-oriented wiki software, it's really hard to collaborate on most kinds of Web content. This makes collaboration a special sort of behavior on the original Web, an exception to a "me first" rule that dominates most publishing. In The Second Web, the ability to any number of people collaborate on any section of a published document is a given - and is accomplished using the same tools common to all documents on The Second Web. Making collaboration a default behavior for publishing, and giving people several ways in which they can collaborate, will change the development of content on The Second Web far more than we can probably imagine today.
- The Second Web is easy to share with specific groups. The original Web had two basic modes for publishing: show content to one very specific group, or to the world. Email gave us some hints as to how we could have overlapping audiences for content, but it was a poor technology at best for sharing content with groups. The Second Web makes it easy for a document or conversation to transition from one person's private content to a small conversation to broader groups or to the world as a whole. This will make it far easier for people on The Second Web to reach and to address very specific kinds of audiences with very specific kinds of messages. The Second Web will become, in effect, millions of specific and overlapping Webs, each with their own particular flavor of conversations and collaborations.
- The Second Web has history. When we look at a Web page, we see a document that has no inherent history: it is whatever the latest image of that document has become. Web archiving services can give us a hint as to how things used to look on the Web, but they lack comprehensiveness. Wikis have some ability to play back specific Web pages, but again this is only available for specific types of content. The Second Web assumes that all of its content has history that needs to be easily accessed and understood, regardless of how it came into being. A personal note can become a conversation which in turn can become a collaboration on a major information source. The Second Web makes it easy to see the history of these progressions - and to understand exactly who did what at which points in that history. This will have a major impact over time on our understanding of history.
- The Second Web fits both personal and professional needs. On the first Web, technologies that supported enterprises were rarely the same as those that were used on the public Web. Oftentimes the only common point of reference was the Web browser: most all of the other underpinnings were separate. This makes it particularly hard for enterprises to integrate their operations efficiently with the original Web. By basing its technologies on a protocol that can serve as a replacement for email-style communications amongst any group of people, The Second Web opens the door to content development that can span both enterprises and the worlds outside of their network firewalls much more easily. More content will be in a similar format with similar ability to be shared and edited collaboratively on any mobile, desktop or household platform with specific groups securely. This may help to fuel new gains in productivity that the original Web promised but sometimes failed to deliver.
Where The Second Web Goes From Here
Right now, we're experiencing the first developing example of The Second Wave via the Google Wave preview application. But this is, after all, just one early example of an HTML 5-based application built on top of the Google Wave protocol and API. Others are already being developed by third party software houses, and there will be more to come as the Wave protocol begins to power other platforms on the Web. We can also expect that there will be technologies competitive to Google Wave that will adopt Second Web concepts and probably interconnect with Wave. For example, if the Twitter or Facebook platform were to open up its server engine as an open -source platform with HTML 5 - compliant APIs, then this might further amplify the landscape of The Second Web, though perhaps with a more limited range of potential uses than available to Google Wave.
Whatever the specific product landscape that may evolve in The Second Web, Google Wave has established its basic landmarks and byways. The Second Web will be a publishing environment that makes it far easier to access, share and organize content in ways that lead to productive and rewarding relationships in any number of groups. We will continue to use and to enjoy the Web as we know it today, even as our homes, vehicles and mobile devices offer us a range of publishing options separate from the Web. It may take several years before The Second Web becomes a major factor in influencing how content markets develop, just as the original Web's introduction was not viewed seriously by many people until it gained some scale in consumer and enterprise markets. But at the frenetic pace of development already established by Google in rolling out the Google Wave preview, it's likely that the tipping point for The Second Web may arrive far earlier than many believe today.
What does this mean to you? Take a deep breath, all of you who have lived through more than a decade of change courtesy of the World Wide Web. As I said recently at an event, it's not that everything that you know is wrong, but we have a lot to learn about what is going to be right in The Second Web. Human communications are about to enter yet another level of universality and immediacy, one that will begin to absorb billions of people who never even had an email account. For these people, they may ask, "What's a Web page?" the same way that people are asking today, "What's a wave?" The "Hello, world" universe of the tiny community now on Google Wave is about to get larger. Much larger. When it does, the speed at which The Second Web becomes THE Web might be staggering.
Main Wave Articles Interesting Waves Guides About
 |
This work and all other works labeled with the ContentWave (TM) trademark by Shore Communications Inc.are licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License. Based on a work at wave.google.com. |
Waveboard - ohne Browser auf der Google Wave
Kaum habe ich (Erik sei dank) Zugang zur schönen neuen Google-Wave-Welt erhalten, musste ich mich gleich nach einem Client dafür umschauen. Und bin mit Waveboard fündig geworden.
Im Prinzip ist das Programm nichts anderes als ein spezialisierter Browser für Google Wave. Also nichts, was ich nicht auch mit Fluid oder Prism hätte selbst basteln können. Jedenfalls entlastet es meinen Arbeitsbrowser von der Darstellung des doch relativ aufwändigen Wave-Frontends. Und es erspart mir - allein wegen Wave - mit meinem Browser permanent bei Google eingeloggt zu sein und damit alle Suchaktivitäten getrackt zu bekommen...
Drei kleine Dinge sind mit dem Selbstbau mittels Fluid nicht zu bewerkstelligen: Waveboard findet mit einem Icon Platz in der Menüleiste und zeigt an, wenn eine Wave geändert wurde. Darüber informiert es auch mittels Growl. Und in den Menüs bietet es (natürlich mit Tastaturkürzeln versehen) die wichtigsten Befehle zum Bearbeiten der Waves.
Ob und wozu Google Wave etwas taugt, kann ich aktuell noch nicht sagen. Die ersten Test-Waves haben mich noch ziemlich verwirrt. Aber dank dieser Doku hege ich die Hoffnung, bald den Durchblick zu gewinnen.
Systemvoraussetzungen: OS X 10.5 (universal)
Download: Waveboard 0.11 (iPhone Version ebenfalls vorhanden)
Lizenz: Freeware (PRO-Version für 9,- Euro)
Falls ich übrigens doch nicht der letzte war, der noch keine Einladung bekommen hatte: ich hätte jetzt auch ein paar zu vergeben... Kurzer Kommentar reicht. Update: sorry, alle Einladungen sind raus.
Wikipedia in Google Wave
Google Wave ist nicht nur eine Mischung aus Wiki und Chat, man kann auch Wikipedia Einträge ganz einfach per Gatget in einen Wave einbinden. Alles was man machen muss, ist die folgende Adresse als Kontakt zu adden und dem Wave hinzuzufügen: wikifier@appspot.com Falls ihr mich auf Google Wave adden wollt, dann gebt multitude08 ein
Questions and an Offer
So there are two desktop/web services I'm curious about now that I have a PC that can handle them. TweetDeck and Cliqset. I don't use Facebook, but would love to have a place where my full twitter stream (not just the friends who use the the 3rd party service), RSS feeds, FriendFeed stuff, etc. can all be piled into one screen. From their websites I can't figure out if either of them do that or would be a waste of my time to download. So:
1) Does anyone out there use them? What is your experience?
2) Does anyone have a suggestion for a better option?
Feel free to leave a comment, send an e-mail, leave me a VM via Google Voice (see widget below)
I also have a handful of Google Wave Invites to share!
Social Media Revolution - Is it a Fad?
via youtube.com
Although this is aimed at marketing people - if you don't get at least some of it you're out of touch - join Facebook, get a Twitter account and watch out for the Google Wave or you could simply be swept away.
