This is odd…you need a mobile
This is odd…you need a mobile phone to sign up for Gmail (or get an invite from a current user). Well, I guess that’s not a whole lot more strange than needing an email address to sign up for an email account.
Advertise here with Carbon Ads
This site is made possible by member support. ❤️
Big thanks to Arcustech for hosting the site and offering amazing tech support.
When you buy through links on kottke.org, I may earn an affiliate commission. Thanks for supporting the site!
kottke.org. home of fine hypertext products since 1998.
kottke.org posts about google
Fun speculation that the purpose of Google’s
Fun speculation that the purpose of Google’s big stock sale is to grease the skids for their entrance into the S&P 500. Lots of new people buy the stock of a company just added to the index and the stock sale would make that inventory available. (Or do they need money to buy Skype? Or are Google execs getting jittery about being in a bubble and want to cash in?)
Back in April 2004, John Rhodes predicted that
Back in April 2004, John Rhodes predicted that Google would do an IM client using Jabber. Tada!
Here’s how to connect to Google’s IM
Here’s how to connect to Google’s IM network with iChat or Adium. The audio works with iChat as well. Not as good as a Google Talk client for OS X, but I guess it’ll have to do.
Download Squad has screenshots and a quick
Download Squad has screenshots and a quick review of Google Talk, Google’s new IM/VoIP app. Doesn’t look Web-based, which is surprising to me. Looks Windows-only as well, which is lame, lame, lame. Update: the Google Talk site appears to be live and letting people d/l the app.
GoogleOS? YahooOS? MozillaOS? WebOS?
Before we get going, here are some alternate titles for this post, just to give you an idea of what I’m trying to get at before I actually, you know, get at it:
- You’re probably wondering why Yahoo bought Konfabulator
- An update on Google Browser, GooOS and Google Desktop
- A platform that everyone can stand on and why Apple, Microsoft, and, yes, even Google will have to change their ways to be a part of it
- The next killer app: desktop Web servers
- Does the Mozilla Foundation have the vision to make Firefox the most important piece of software of this decade?
- Web 3.0
- Finally, the end of Microsoft’s operating system dominance
Now that your hyperbole meter has pegged a few times, hopefully the rest of this will seem tame in comparison. (And apologies for the length…I got rolling and, oops, 2500 words. But many of them are small so…)
Way back in October 2004, this idea of how the Web as a platform might play out popped into my head, and I’ve been trying to motivate myself into writing it down ever since. Two recent events, Yahoo’s purchase of Konfabulator and Google’s release of a new beta version of Google Desktop have finally spurred me into action. But back to October. At the Web 2.0 conference, Stewart pulled me aside and said something like, “I think I know what Google is doing with Google Browser.” From a subsequent post on his site:
I’ve had this post about Adam Bosworth, Alchemy and the Google browser sitting around for months now and it is driving me crazy, because I want all the credit for guessing this before it happens. So, for the record, if Google is making a browser, and if it is going to be successful, it will be because there is a sophisticated local caching framework included, and Google will provide the reference apps (replying to emails on Gmail or posting messages to Google groups while on the plane).
At the time, Adam Bosworth had been recently hired by Google for purposes unknown. In a blog post several months before he was hired, Bosworth mused about a “new browser”:
In this entry, I’m going to discuss how I imagine a mobilized or web services browser handles changes and service requests when it isn’t connected. This is really where the peddle hits the metal. If you just read data and never ever alter it or invoke related services (such as approving an expense report or booking a restaurant) then perhaps you might not need a new browser. Perhaps just caching pages offline would be sufficient if one added some metadata about what to cache. Jean Paoli has pointed out to me that this would be even more likely if rather than authoring your site using HTML, you authored it as XML “pages” laid out by the included XSLT stylesheets used to render it because then you could even use the browser to sort/filter the information offline. A very long time ago when I was still at Microsoft (1997) we built such a demo using XSLT and tricky use of Javascript to let the user do local client side sorting and filtering. But if you start actually trying to update trip reports, approve requests, reserve rooms, buy stocks, and so on, then you have Forms of some sort, running offline, at least some of the time, and code has to handle the inputs to the “Forms” and you have to think through how they are handled.
A couple weeks later, Google introduced the first iteration of their Desktop Search. To me, the least interesting thing about GDS was the search mechanism. Google finally had an application that installed on the desktop and, even better, it was a little Web server that could insert data from your local machine into pages you were browsing on google.com. That was a new experience: using a plain old Web browser to run applications locally and on the Web at the same time.
So this is my best guess as to how an “operating system” based on the Web (which I will refer to as “WebOS”) will work. There are three main parts to the system:
- The Web browser (along with other browser-ish applications like Konfabulator) becomes the primary application interface through which the user views content, performs services, and manages data on their local machine and on the Web, often without even knowing the difference. Something like Firefox, Safari, or IE…ideally browser agnostic.
- Web applications of the sort we’re all familiar with: Gmail, Flickr, and Bloglines, as well as other applications that are making the Web an ever richer environment for getting stuff done. (And ideally all Ajaxed up to provide an experience closer to that of traditional desktop apps.)
- A local Web server to handle the data delivery and content display from the local machine to the browser. This local server will likely be highly optimized for its task, but would be capable of running locally installed Web applications (e.g. a local copy of Gmail and all its associated data).
That’s it. Aside from the browser and the Web server, applications will be written for the WebOS and won’t be specific to Windows, OS X, or Linux. This is also completely feasible, I think, for organizations like Google, Yahoo, Apple, Microsoft, or the Mozilla Foundation to make happen (more on this below).
Compared to “standalone” Web apps and desktop apps, applications developed for this hypothetical platform have some powerful advantages. Because they run in a Web browser, these applications are cross platform (assuming that whoever develops such a system develops the local Web server part of it for Windows, OS X, Linux, your mobile phone, etc.), just like Web apps such as Gmail, Basecamp, and Salesforce.com. You don’t need to be on a specific machine with a specific OS…you just need a browser + local Web server to access your favorite data and apps.
For application developers, the main advantage is that instead of writing two or more programs for multiple platforms (one for the Web, one for Windows, etc.), they can write one app that will run on any machine with the WebOS using the same code base. Bloglines and NetNewsWire both do about the same thing and have radically different codebases (Bloglines uses HTML/JavaScript + some sort of backend programming/scripting language while NNW is a Cocoa app only for OS X), but a version of Bloglines developed for the above platform could utilize a single codebase.
You also get the advantages of locally run applications. You can use them when you’re not connected to the Internet. There could be an icon in the Dock that fires up Gmail in your favorite browser. For applications using larger files like images, video, and audio, those files could be stored and manipulated locally instead of waiting for transfer over the Internet.
There are also disadvantages to WebOS applications, not the least of which[1] is that HTTP+JavaScript+XHTML+CSS+Flash is not as robust in providing functionality and user interaction as true desktop applications written in Cocoa or Visual Basic. But as Paul Graham points out, Web applications may be good enough[2]:
One thing that might deter you from writing Web-based applications is the lameness of Web pages as a UI. That is a problem, I admit. There were a few things we would have really liked to add to HTML and HTTP. What matters, though, is that Web pages are just good enough.
Web pages weren’t designed to be a UI for applications, but they’re just good enough. And for a significant number of users, software that you can use from any browser will be enough of a win in itself to outweigh any awkwardness in the UI. Maybe you can’t write the best-looking spreadsheet using HTML, but you can write a spreadsheet that several people can use simultaneously from different locations without special client software, or that can incorporate live data feeds, or that can page you when certain conditions are triggered. More importantly, you can write new kinds of applications that don’t even have names yet.
And how about these new kinds of applications? Here’s how I would envision a few apps working on the WebOS:
- Gmail. While online, you read your mail at gmail.com, but it also caches your mail locally so when you disconnect, you can still read it. Then when you connect again, it sends any replies you wrote offline, just like Mail.app or Outlook does. Many people already use Gmail (or Yahoo Mail) as their only email client…imagine if it worked offline as well.
- A Web version of iTunes. Just like the desktop version of iTunes, except in the browser. Manages/plays audio files stored locally, with an option to back them up on the server (using .Mac or similar) as well. iTunes already utilizes information from the Internet so well (Web radio, podcasting iTMS, CDDB, etc.) that it’s easy to imagine it as a Web app. (And why stop at audio…video would work equally as well.)
- Flickr. Manage image files locally and on Flickr’s server in the browser. You could even do some rudimentary photo manipulation (brightness, contrast, red-eye correction, etc.) in the browser using JavaScript or even Flash. Prepare a bunch of photos for uploading to Flickr while on the plane ride home and they automatically sync when you next connect to the Internet.
- Newsreader. Read sites while offline (I bet this is #1 on any Bloglines user’s wish list). Access your reading list from any computer with a browser (I bet this is #1 on any standalone newsreader user’s wish list).
- File backup. A little WebOS app that helps you back up your files to Apple’s .Mac service, your ISP, or someone like Google. You’ll specify what you want backed up and when through the browser and the backup program will take care of the rest.
I’m looking at the rest of the most commonly used apps on my Powerbook and there’s not too many of them that absolutely need to be standalone desktop applications. Text editor, IM[3], Word, Excel, FTP, iCal, address book…I could imagine versions of these running in a browser.
So who’s going to build these WebOS applications? Hopefully anyone with XHTML/JavaScript/CSS skills, but that depends on how open the platform is. And that depends on whose platform it is. Right now, there are five organizations who are or could be moving in this direction:
- Google. If Google is not thinking in terms of the above, I will eat danah’s furriest hat. They’ve already shifted the focus of Google Desktop with the addition of Sidebar and changing the name of the application (it used to be called Google Desktop Search…and the tagline changed from “Search your own computer” to the more general “Info when you want it, right on your desktop”). To do it properly, I think they need their own browser (with bundled Web server, of course) and they need to start writing their applications to work on OS X and Linux (Google is still a Windows company)[4]. Many of the moves they’ve made in the last two years have been to outflank Microsoft, and if they don’t use Google Desktop’s “insert local code into remote sites” trick to make whatever OS comes with people’s computers increasingly irrelevant, they’re stupid, stupid, stupid. Baby step: make Gmail readable offline.
- Yahoo. I’m pretty sure Yahoo is thinking in these terms as well. That’s why they bought Konfabulator: desktop presence. And Yahoo has tons of content and apps that that would like to offer on a WebOS-like platform: mail, IM, news, Yahoo360, etc. Challenge for Yahoo: widgets aren’t enough…many of these applications are going to need to run in Web browsers. Advantages: Yahoo seems to be more aggressive in opening up APIs than Google…chances are if Yahoo develops a WebOS platform, we’ll all get to play.
- Microsoft. They’re going to build a WebOS right into their operating system…it’s likely that with Vista, you sometimes won’t be able to tell when you’re using desktop applications or when you’re at msn.com. They’ll never develop anything for OS X or for Linux (or for browsers other than IE), so its impact will be limited. (Well, limited to most of the personal computers in the world, but still.)
- Apple. Apple has all the makings of a WebOS system right now. They’ve got the browser, a Web server that’s installed on every machine with OS X, Dashboard, iTMS, .Mac, Spotlight, etc. All they’re missing is the applications (aside from the Dashboard widgets). But like Microsoft, it’s unlikely that they’ll write anything for Windows or Linux, although if OS X is going to run on cheapo Intel boxes, their market share may be heading in a positive direction soon.
- The Mozilla Foundation. This is the most unlikely option, but also the most interesting one. If Mozilla could leverage the rapidly increasing user base of Firefox and start bundling a small Web server with it, then you’ve got the beginnings of a WebOS that’s open source and for which anyone, including Microsoft, Google, Yahoo, and anyone with JavaScript chops, could write applications. To market it, they could refer to the whole shebang as a new kind of Web browser, something that sets it apart from IE, a true “next generation” browser capable of running applications no matter where you are or what computer (or portable device) you’re using.
So yeah, that’s the idea of the WebOS (as I see it developing) in a gigantic nutshell. The reality of it will probably be a lot messier and take a lot longer than most would like. If someone ends up doing it, it will probably not be as open as it could be and there will likely be competing Web platforms just as there are now competing search engines, portals, widget applications (Konfabulator, Dashboard, Google Desktop Sidebar), etc., but hopefully not. There’s lots more to discuss, but I’m going to stop here before this post gets even more ridiculously long. My thanks if you even made this far.
[1] Actually, the biggest potential problems with all this are the massive security concerns (a Web browser that has access to data on your local hard drive?!!!??) and managing user expectations (desktop/web app hybrids will likely be very confusing for a lot of users). Significant worries to be sure, but I believe the advantages will motivate the folks developing the platform and the applications to work through these concerns.
[2] For more discussion of Web applications, check out Adam Rifkin’s post on Weblications.
[3] Rumor has it that Google is releasing an IM client soon (more here). I’ll be pretty surprised if it’s not significantly Web-based. As Hotmail proved for email, there’s no reason that IM has to happen in a desktop app (although the alerting is problematic).
[4] Maybe Google thinks they can’t compete with Apple’s current offerings (Spotlight, Dashboard, Safari, iPhoto) on their own platform, but that’s not a good way of thinking about it. Support as many people as you can on as many different architectures as you can, that’s the advantage of a Web-based OS. Microsoft certainly hasn’t thought of Apple as a serious competitor in the OS space for a long time…until Web applications started coming of age recently, Microsoft’s sole competitor has been Microsoft.
It’s sad to see O’Reilly selling PageRank
It’s sad to see O’Reilly selling PageRank to all these mortgage and hotel sites that have thoroughly polluted Google with their bad results. Much of the onus is on Google to clean that stuff out, but as Rogers notes in the thread, “if you’re going to sell sponsored links, you should take the time to make sure they are advertisers you’d want to be associated with”. O’Reilly is the kind of company that people believe in (a rare thing in today’s world), but this makes me believe in them a little less.
Google introduces a new (beta) version of
Google introduces a new (beta) version of Google Desktop featuring Sidebar, their answer to Dashboard and Konfabulator. Here’s more on Google’s move from the Times, which also includes speculation on the possible release of an IM client this week.
How did a site dealing with digital
How did a site dealing with digital video codecs become the place for lonely people to go on the web? Moviecodec.com is still the second result for the “i am lonely” search on Google; here’s the thread in question.
Odd size comparison of Yahoo and Google
Odd size comparison of Yahoo and Google indices. I think their assumption (that a “series of random searches to both search engines should return more than twice as many results from Yahoo! than Google”) is pretty flawed. The number of returned results could vary because of the sites’ different optimizations for dictionary words, for searches with small result sets, and differences in how their search algorithms include or exclude relevant results. Put it this way: if I’m looking for a frying pan in my apartment, I’m gonna refine my search to the kitchen and not worry about the rest of the house, no matter how large it is. (via /.)
Google corporate timeline. Might be old, but
Google corporate timeline. Might be old, but I’ve never seen it before. (via Subtraction)
Google attempting to patent RSS advertising?
John Battelle points to news of Google (the author is Nelson Minar) attempting to patent the idea of automating the incorporation of targetted ads into RSS files. Here’s the application on the USPTO site. I’ve got a few questions and concerns:
Is this a joke?
Ok, bad first question since it seems unlikely that Nelson and Google would write up this application just to have a few laughs. So here’s a better question: where’s the prior art on this? The patent was filed on 12/31/2003. I floated the idea of embedding advertising into RSS ads in October 2002 and there was prior art then. But Google’s patent application covers “targeted ads” in a “syndicated, e.g., RSS, presentation format in an automated manner”. Curiously, I believe this is already covered by an older Google patent, filed in 12/2002:
The relevance of advertisements to a user’s interests is improved. In one implementation, the content of a web page is analyzed to determine a list of one or more topics associated with that web page. An advertisement is considered to be relevant to that web page if it is associated with keywords belonging to the list of one or more topics. One or more of these relevant advertisements may be provided for rendering in conjunction with the web page or related web pages.
That’s Google AdSense in a nutshell: inserting targeted ads into web documents in an automated manner. So what is it about RSS/Atom files that make them different than plain old web pages and hence not covered under the 2002 AdSense patent? Nothing. This vocabulary of “feeds” and “syndication” is still misleading. RSS/Atom files, especially as they are described in the 12/2003 patent application, are XML files that sit on a web server waiting for someone with a web browser to come along to read them, just like XHTML files:
So, people access documents written in a markup language that have been published on a Web server with a software application. If this seems familiar to you, it should. It’s called Web browsing and has nothing to do with syndication. RSS readers and newsreaders are just specialized Web browsers…
The 12/2003 application tries to explain the difference between HTML pages and “syndicated content formats” thusly:
Syndicated content, unlike web pages which are normally stored in an HTML format, are often stored and presented in what may be described as a syndicated content format. Syndicated content formats are often XML (eXtended Markup Language) based and include structured representations of content such as news articles, search results, and web log entries. Syndicated content formats are primarily intended for providing syndicated information, e.g., news headlines, weblogs, etc. in a structured format such as a list of items, with another device, e.g., a user device, usually controlling the ultimate presentation format of the items in the list. This is in contrast to HTML which usually includes a fair amount of presentation and formatting information within an HTML document such as a web page.
That’s a pretty weak explanation and sounds a lot like what a web browser (the “user device” that controls the presentation) does with XHTML files (XML-based files without a “fair amount of presentation and formatting information”). It sounds to me like Google already has this covered with their previous patent.
[Long aside: Does the prior art of embedding AdSense ads in XHTML files invalidate this patent? Patents are tricky because they don’t cover ideas, they cover specific implementations of ideas. While the 12/2003 application states that “said syndicated format is an XML compliant format” it also specifies that “said syndicated format is a format for listing items corresponding to a channel, said received information including a listing of at least two items and including for each item, a title and a link”. That is, the XML files they’re talking about have to be RSS/Atom-ish in nature. This doesn’t rule out XHTML files in theory, but it does rule out many of them in practice.
But the really tricky part with these software patents is that the implementations of ideas are written so broadly that they might as well be patents of the ideas themselves. If you look at it that way (the patent-holding companies certainly seem willing to litigate on that basis), Google has already embedded automated, targeted advertising into XML-based files. According to news.com, Google launched their AdSense service in June 2003. When the first AdSense advertisement was embedded in an XHTML file soon after that, well, there’s your prior art on the very thing that Google attempted to patent 6 months later.]
Yahoo! buys Konfabulator
Yahoo! buys Konfabulator. This could be huge. Aside from the Flickr purchase, this is the first move by Yahoo! that gives them something that Google needs but doesn’t have. (More on this soon.)
Google Moon: explore the Apollo landing sites
Google Moon: explore the Apollo landing sites in the Google Maps interface.
NewsRank but not particularly new
I missed this April article in New Scientist about Google’s plans to rank news stories according to quality and credibility of the sources:
Now Google, whose name has become synonymous with internet searching, plans to build a database that will compare the track record and credibility of all news sources around the world, and adjust the ranking of any search results accordingly.
The database will be built by continually monitoring the number of stories from all news sources, along with average story length, number with bylines, and number of the bureaux cited, along with how long they have been in business. Google’s database will also keep track of the number of staff a news source employs, the volume of internet traffic to its website and the number of countries accessing the site.
Google will take all these parameters, weight them according to formulae it is constructing, and distil them down to create a single value. This number will then be used to rank the results of any news search.
The second paragraph of the story mentions that this system has been patented by Google, but I don’t see how it’s much different than what PageRank does or what Metacritic has been doing with film, game, and book reviews:
This overall score, or METASCORE, is a weighted average of the individual critic scores. Why a weighted average? When selecting our source publications, we noticed that some critics consistently write better (more detailed, more insightful, more articulate) reviews than others. In addition, some critics and/or publications typically have more prestige and weight in the industry than others. To reflect these factors, we have assigned weights to each publication (and, in the case of film, to individual critics as well), thus making some publications count more in the METASCORE calculations than others.
I wonder if these systems will eventually let their users tweak the credibility algorithms to their liking. For instance, it won’t take long for conservatives to start complaining about the liberal bias of Google News. In the case of Metacritic, I’d like them to ignore Anthony Lane’s rating when he writes about summer blockbusters and put greater emphasis on whatever Ebert has to say. In the meantime, I’m readying my patent applications for RecipeRank, PhotoRank, ModernFurnitureRank, SoftDrinkRank, and, oooh, PatentRank. I’m sure they’re brilliantly unique enough to be recognized by the US Patent Office as new inventions.
Another use for Google Maps: getting out
Another use for Google Maps: getting out of traffic tickets in the courtroom. Many traffic cases are decided in favor of the state because of a lack of information on the part of the defendant…you’d be surprised at how good a chance you have of fighting a ticket if you show up armed with good information.
Paul’s really personal Google News
Paul’s really personal Google News. “Paul comes late to work, again”.
Google, Hearst, and Goldman Sachs invest $100 million
Google, Hearst, and Goldman Sachs invest $100 million in company that delivers broadband over conventional power lines. I had no idea such a thing was being done. This could be huge for rural areas in the US and abroad.
Google Maps hack: Iraq War casualty map
Google Maps hack: Iraq War casualty map. “This page shows the progession of US military casualties from the Iraq war. Each click displays 30 more casualties, starting from the beginning of the war. Each soldier is shown in at their home town. Click their icon for more details.”
Google is doing an online payment system,
Google is doing an online payment system, but will not be competing with PayPal.
Giant-Ass Image Viewer
Giant-Ass Image Viewer. Python script (+JavaScript and CSS) for cutting up and viewing large images, a la Google Maps.
Google Wallet
Word on the street (via waxy) is that Google is set to release a PayPal competitor called Google Wallet. A thread at Techdirt notes that Yahoo!, Microsoft, and eBay have all tried to launch similar services that met with little or no success in the face of competition with PayPal.
I doubt Google is focused on competing with PayPal, at least in the short term. This move, if true, makes a lot of sense for Google. They already have an internal payment system set up to collect and distribute AdSense revenues, a store selling t-shirts, bean bags, search hardware, they sell software, and they’ve indicated that with Google Video, people will be able to charge others to view videos uploaded to Google’s servers (with Google taking a small cut). Taking the core of that internal payment system, it would probably be technologically trivial** for them to open it up for anyone to pay money to anyone else (instead of just individual —> Google or Google —> individual). The line above about their Google Video plans — “people will be able to charge others to view videos uploaded to Google’s servers (with Google taking a small cut)” — already sounds a lot like what PayPal does. This is the Andre Torrez school of product development…build something that solves a problem you’re having and it’ll probably be useful to a bunch of other people if you let them use it too.
Plus it leverages their existing user base. If you’ve already got an AdSense account or are going to charge for your video through Google Video, you’re already a GWallet user…and signing people up through their GMail/Orkut/Blogger accounts would probably be pretty easy as well. This move may also indicate that Google is planning to charge a wider range of people for products/services — maybe a “pro” version of Gmail, a robust, commercial API to their search results, or even a music store? GWallet would be needed infrastructure for ramping up from paying relatively few AdSense users to (potentially) anyone who uses Google. It makes sense for them beyond trying to gain a foothold in the online payments space.
** Getting the banking stuff sorted out is another story though…but as PayPal has shown, if you can get that set up, there’s plenty of revenue to be had.
Nokia.com comes up first in a
Nokia.com comes up first in a Google search for “motorola mobile phones”. I suspect it’s because Motorola’s site isn’t optimized for Google (lots of Flash, little text) and a difference in usage: it’s “cell phones” in the US versus “mobile phones” in Europe (where Nokia is from).
Google Sightseeing highlights interesting satellite photos taken from Google Maps
Google Sightseeing highlights interesting satellite photos taken from Google Maps.
A first look at Google Earth, the
A first look at Google Earth, the replacement for the Keyhole mapping software. “View Railroads, Subway lines and Bus routes along with all their stops. Or select multiple locations and have Google give you directions.”
Stay Connected