<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>louisgray.com - Latest Comments in Twitter's Search Engine Is Very, Very, Broken</title><link>http://louisgray.disqus.com/</link><description>A Silicon Valley Blog for Early Adopters and Tech Geeks</description><atom:link href="https://louisgray.disqus.com/louisgraycom_twitters_search_engine_is_very_very_broken/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 01 Jun 2009 06:35:47 -0000</lastBuildDate><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-10347136</link><description>&lt;p&gt;There is an offiziell Twitter issue.. now.&lt;/p&gt;&lt;p&gt;&lt;a href="http://twitter.zendesk.com/forums/31935/entries/38518" rel="nofollow noopener" target="_blank" title="http://twitter.zendesk.com/forums/31935/entries/38518"&gt;http://twitter.zendesk.com/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Marco</dc:creator><pubDate>Mon, 01 Jun 2009 06:35:47 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-10254886</link><description>&lt;p&gt;Do you know that we are closed to the 2 billionth tweet ?&lt;/p&gt;&lt;p&gt;See &lt;a href="http://www.tweespeed.com" rel="nofollow noopener" target="_blank" title="http://www.tweespeed.com"&gt;http://www.tweespeed.com&lt;/a&gt; which gives the "instant speed of twitter" and try to estimate the reaching date. Amazing.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pascal</dc:creator><pubDate>Fri, 29 May 2009 09:13:07 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9950203</link><description>&lt;p&gt;No kidding Twitter search is broken.  None of my tweets over the last nine days (&lt;a href="http://www.twitter.com/jaysbryant)" rel="nofollow noopener" target="_blank" title="http://www.twitter.com/jaysbryant)"&gt;http://www.twitter.com/jays...&lt;/a&gt; show up in the search.  For some reason my account has been excluded from the twitter search.  No explanation yet from Twitter.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jay Bryant</dc:creator><pubDate>Tue, 26 May 2009 09:16:07 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9948056</link><description>&lt;p&gt;Interesting post Louis.&lt;/p&gt;&lt;p&gt;The element that's bugging me right now, is how useless Twitter's 'trending topics' feature has become; thanks to spam.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jim Connolly</dc:creator><pubDate>Tue, 26 May 2009 06:26:41 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9823439</link><description>&lt;p&gt;Louis,&lt;/p&gt;&lt;p&gt;What I find interesting is that despite search potentially being a key asset for Twitter, the better and more useful search applications are being created by third-parties such as Twazzup and Twingly.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Evans</dc:creator><pubDate>Sat, 23 May 2009 07:41:30 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9815432</link><description>&lt;p&gt;@Paul - you can't give Twitter any slack when comparing it to email because the retards that built Twitter should have learned how to architect a system to handle any amount of traffic. It's not that hard. As Scoble and many others point out - FriendFeed can handle much more complex data problems. #TwitterSucks&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Bean</dc:creator><pubDate>Fri, 22 May 2009 22:00:19 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9809132</link><description>&lt;p&gt;I suppose that's a defensible argument. :)&lt;/p&gt;&lt;p&gt;The problem, however, doesn't appear to be explicitly about money. Rather, it's the scale of the engineering challenges they're up against. I find myself wishing I could be a fly on the wall at Twitter -- this is a team that simply must be pulling their hair out to rectify the fruits of early engineering shortcuts regarding integration (search from Summize) and scaling. I've been commenting (apparently) negatively about Twitter lately -- I absolutely adore the service were it not for two things. First, it's unreliable. Second, I want more control to reduce noise. The perfect fix for both of these issues for me has been FriendFeed of late, but I'm still on Twitter and support what their doing. Really looking forward to substance coming out of Twitter HQ in the coming weeks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PeteWright</dc:creator><pubDate>Fri, 22 May 2009 17:37:18 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9808956</link><description>&lt;p&gt;Remember that email was first available in 1974, and it took a couple of decades before it became the tool we all know and use, today. Twitter needs to be around for a bit longer before it is given parity with email, regardless of Moore's Law and its effect on new technology adoption.&lt;/p&gt;&lt;p&gt;That being said, I definitely agree that Twitter needs an angel with experience in scaling. It probably (should have) realized this pretty early on, when the explosion in users was first detected and projections for the future were being developed. It's really just a matter of money ... and that's probably what's slowing things down. I mean, when will Twitter become profitable? For that matter, HOW will they become profitable? At least Google, Microsoft and Apple (by far the least experienced of the three) have deep pockets and well-monetized public channels.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul</dc:creator><pubDate>Fri, 22 May 2009 17:30:04 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9802044</link><description>&lt;p&gt;Well put. It's a free service, and you get what you pay for. It does some things well, some things poorly. And a catch 22 - Twitter could offer premium service, but could they support it?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">piers</dc:creator><pubDate>Fri, 22 May 2009 14:16:49 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9801682</link><description>&lt;p&gt;Thank you! I couldn't agree more, and found this argument annoying - the way-back machine is watching you no matter what you do anyways.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">piers</dc:creator><pubDate>Fri, 22 May 2009 14:06:23 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9800382</link><description>&lt;p&gt;Twitter itself has been a case study in scalability issues since their beginning.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Ballance</dc:creator><pubDate>Fri, 22 May 2009 13:24:02 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9819016</link><description>&lt;p&gt;That's pretty egregious stuff.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Josh Haley</dc:creator><pubDate>Fri, 22 May 2009 12:55:00 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9819013</link><description>&lt;p&gt;Ari, great article - you should have added Google to that list as well.  I usually just use Google to do my Twitter search, using "&lt;a href="site:Twitter.com" rel="nofollow noopener" target="_blank" title="site:Twitter.com"&gt;site:Twitter.com&lt;/a&gt;" - it has been much more effective than &lt;a href="http://search.twitter.com" rel="nofollow noopener" target="_blank" title="search.twitter.com"&gt;search.twitter.com&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jesse Stay</dc:creator><pubDate>Fri, 22 May 2009 12:08:00 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9797959</link><description>&lt;p&gt;I think we are forgetting that implementing a good search engine takes quite lot of effort. Twitter will need more than an handful of PHP/Scala (or whatever they use) developers to come even close to a fraction of what google can do. A deal would make sense at this point. Of course, if Twitter has the money, they should grow it inside. But Twitter doesn't have that much time to be messing around.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jose Sandoval</dc:creator><pubDate>Fri, 22 May 2009 12:07:41 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9797957</link><description>&lt;p&gt;I haven't had the kindest words for Twitter Search: &lt;a href="http://thenoisychannel.com/?s=twitter+search" rel="nofollow noopener" target="_blank" title="http://thenoisychannel.com/?s=twitter+search"&gt;http://thenoisychannel.com/...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;But I think some of the comments here are overkill. I use Twitter search regularly as an alerting service for a broad vanity query. It works reasonably well, and I've learned to live with the glitches as part of what comes along with a free service. Could they do a lot better? For sure, and I've blogged about that. But what they have now is nonetheless useful.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Tunkelang</dc:creator><pubDate>Fri, 22 May 2009 12:07:39 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9797771</link><description>&lt;p&gt;Good for "right now" responses is Twitter's beauty. And maybe that's all Twitter search will ever be, although I hold out hope for more, like you.&lt;/p&gt;&lt;p&gt;Louis, you're the one who keeps bringing up FriendFeed whenever critiquing Twitter, not me. I see them as two complementary, but vastly different, social tools. FriendFeed competes w/ Facebook, not Twitter.&lt;/p&gt;&lt;p&gt;Peace!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BarbaraKB</dc:creator><pubDate>Fri, 22 May 2009 12:01:14 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9819012</link><description>&lt;p&gt;Have you seen the review of other search engines I wrote at &lt;a href="http://mashable.com/2009/04/22/twitter-search-services/" rel="nofollow noopener" target="_blank" title="http://mashable.com/2009/04/22/twitter-search-services/"&gt;http://mashable.com/2009/04...&lt;/a&gt; yet?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ari Herzog</dc:creator><pubDate>Fri, 22 May 2009 11:56:00 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9797409</link><description>&lt;p&gt;True, but I think they've just been busy integrating the results in to the main interface.&lt;/p&gt;&lt;p&gt;But one thing that really bugs me is that they still keep deleted tweets in the results. When I delete a tweet, for whatever reason, I want it deleted. (Rather like the stories around yesterday about photos not being deleted) - It just seems they don't re-index things much, if at all. They just sit across 'the firehose', suck it all in and that's it.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kosso</dc:creator><pubDate>Fri, 22 May 2009 11:49:02 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9793318</link><description>&lt;p&gt;Barbara, the fact that it is not stable, and that I couldn't find basic things I was looking for absolutely diminishes its usefulness as a search engine. How can you say that falsely declaring no results or flat-out failures doesn't diminish it? What we know is that it is good for "right now" responses, but anything deeper, and you're dead.&lt;/p&gt;&lt;p&gt;As for FriendFeed vs. Twitter, that's not this article. I've already written that one a few times. The good news is that FriendFeed has a viable, true, searchable index.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Louis Gray</dc:creator><pubDate>Fri, 22 May 2009 11:05:49 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9793265</link><description>&lt;p&gt;If Twitter were going back to the well for more money, I would hope they could prove that "this time" they could scale and meet growth requirements. If they cannot, they need to come clean on what we can expect from the service, and what we should not expect.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Louis Gray</dc:creator><pubDate>Fri, 22 May 2009 11:03:55 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9793234</link><description>&lt;p&gt;The "removing tweets on request" issue is a tough one. The tendency would be to blame the user for some ill-sent tweets. Just like Google won't remove a page you wish would go away, I think the current usage pattern is fine.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Louis Gray</dc:creator><pubDate>Fri, 22 May 2009 11:02:39 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9793194</link><description>&lt;p&gt;I agree with your comments on Twitter's cloak of secrecy being a huge issue. Were they hoping nobody would notice their search engine had been deprecated? A quick note saying "Hey! We're more popular than ever and struggling to keep up, so we're limiting searches to the last two weeks" would be absolutely acceptable, and the grumbling would be lighter.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Louis Gray</dc:creator><pubDate>Fri, 22 May 2009 11:00:58 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9792969</link><description>&lt;p&gt;Even if it worked well, there is some flexibility missing in their search.&lt;/p&gt;&lt;p&gt;For example, on &lt;a href="http://twitter.com" rel="nofollow noopener" target="_blank" title="twitter.com"&gt;twitter.com&lt;/a&gt;, we cannot search profile information. Only user names, first name, last name. As a user, I was trying to find out someone I had followed but forget the name but could not do any search based on the information I remembered.&lt;/p&gt;&lt;p&gt; I see Twitter search like a proof of concept. It has lot of potential but it can't be fully exploited yet.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jerome Paradis</dc:creator><pubDate>Fri, 22 May 2009 10:54:12 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9791868</link><description>&lt;p&gt;Let the principle of Default behaviour prevail &lt;a href="http://tr.im/m6p6" rel="nofollow noopener" target="_blank" title="http://tr.im/m6p6"&gt;http://tr.im/m6p6&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vinko</dc:creator><pubDate>Fri, 22 May 2009 10:19:07 -0000</pubDate></item><item><title>Re: Twitter's Search Engine Is Very, Very, Broken</title><link>http://blog.louisgray.com/2009/05/twitter-search-engine-is-very-very.html#comment-9791224</link><description>&lt;p&gt;I'm glad you did show the superior FF search as a counterpoint to Twitter's latest folly.  That kept me nodding along throughout the article.  FF search is extremely powerful and I still find myself using it several times a day - mostly as a supplement to my hazy memory of interesting things people have said in the past.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel J. Pritchett</dc:creator><pubDate>Fri, 22 May 2009 09:56:16 -0000</pubDate></item></channel></rss>