Commentary

Michael Hickins
 

How Fast Will Google Index Twitter?

It seems that even Google has fallen sway to the Twitterocalypse that is shattering preconceptions about social activity on the Web. I mean, who knew that people would not only broadcast their every move, but that other people would want to read about it?

It seems that even Google has fallen sway to the Twitterocalypse that is shattering preconceptions about social activity on the Web. I mean, who knew that people would not only broadcast their every move, but that other people would want to read about it?Who knew that microblogging would grow into something for everyone -- as a pool for market research, as sources for analysts and reporters, and even as a possible replacement for the emergency broadcast system.

Well, it turns out that Google co-founder Larry Page "always" knew, telling Loic LeMeur that people laughed at him when he talked about realtime search, but now they know the bitter truth. "Not everybody needs sub-second indexing but people are getting pretty excited about realtime," he said.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Google CEO Eric Schmidt, who not too long ago dismissed Twitter as a "poor man's e-mail system," also now admits that Twitter does a "great job" at doing realtime search. (By the way, do Page and Schmidt really say realtime as one word, just like New York Post gossip columnists talk about canoodling stars being "thisclose?")

Schmidt's comments will undoubtedly lead to more speculation that Google will acquire Twitter -- a notion Schmidt immediately tried to snuff in the cradle by saying that Google doesn't have to buy a company to work with it, since "the whole principle of the Web is people can talk to each other."

The "talk to each other" in Schmidt's comment referred to the possibility of Google negotiating a partnership with Twitter, but "talk to each other" is also the whole point about Twitter. It's not just about broadcasting -- it's also about listening, and if you take those two elements, what you get is a conversation. And conversation is the one thing you can't do on Google search.

Google is not about conversation -- it's about searching for information. Now, the wonderful thing about Twitter is the speed with which you can find certain kinds of information, but the awful thing about Twitter is the speed with which you can find certain kinds of misinformation.

So how will Google and Twitter resolve those philosophical differences?

I think Google will soon announce a deal allowing it to index Twitter -- it certainly has the firepower to do so -- but will display results on a separate page, like it does for News, Finance and other categories. This would allow users to decide for themselves whether they want to find out what people are saying about the iPhone right now, or news about the iPhone, or simply product information.

Nicholas Carr took a tough shot at Google today with regards to Google's arrogance -- and it is breathtaking. But Carr's point was that Google boasted about the speed of its search results (and the life-saving qualities of that speed) when that suited its corporate narrative, and then dumped the rules that created that speed when its business model changed. Its regard for the lives it was supposed to be saving took a back seat to financial imperatives.

Indexing Twitter will give Google back the speed it lost when it started serving graphical ads -- and then some. But Twitter searches are unlikely to provide solutions to life-threatening issues, nor will a deal to index Twitter do anything to diminish the sense that Google is turning out to be a company like any other, only much, much bigger.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links