<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2009:/1/tag:www.readwriteweb.com,2009://1.13959-</id>
  <updated>2009-11-23T17:31:10Z</updated>
  <title>Comments for Twitter Track is Back Thanks to New Service from Particls</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=13959" title="Twitter Track is Back Thanks to New Service from Particls" />
    <published>2009-02-23T13:44:18Z</published>
    <updated>2009-02-23T23:17:31Z</updated>
    <title>Twitter Track is Back Thanks to New Service from Particls</title>
    <summary>Twitter Track is Back Thanks to New Service from Particls</summary>
    <author>
      <name>Sarah Perez</name>
      <uri>http://www.sarahintampa.com</uri>
    </author>
    
    <category term="Features" />
    
    <category term="Products" />
    
    <category term="Twitter" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img alt="particls_logo.png" src="http://www.readwriteweb.com/images/particls_logo.png"><a href="http://www.particls.com/">Particls</a>, the one-time RSS feed organizer and alerting service, has today launched a new project they're calling "Particls Fountain." Although it's hinted that the service will eventually do much more, today its goal is simple. Particls Fountain will function as a replacement for the long-gone <a href="http://evhead.com/2007/09/twitter-track.asp">Twitter Track</a> feature that once allowed you to follow topics of interest by keyword.</p>]]>
      <![CDATA[

<p>Unlike its predecessors, the new service from Particls is simple and straightforward. There's little setup involved to get started with Fountain; just choose the method that works for you. You can use Fountain in one of two ways: via Google Talk (or any XMPP client) or via Twitter itself.</p>

<h2>Using Particls with Twitter:</h2>

<p>For Twitter users, just follow <a href="http://www.twitter.com/particls">@particls</a> on Twitter. To track something, start your request with 'd particls.' </p>

<p><u>Example:</u> </p>

<p><strong>d particles follow "web 2.0" </strong></p>

<p>will track all references to "web 2.0" on Twitter. </p>

<p><strong>d particles follow "web 2.0", "web 3.0"</strong></p>

<p>will track all references to "web 2.0" and "web 3.0"</p>

<h2>Using Particls via IM:</h2>

<p>If you would rather use your instant messaging program to be alerted about your tracked keywords, you can do so with any XMPP client, including Google Talk. To get started, just follow <a href="mailto:particls@particls.com">particls@particls.com</a>. You can then use the following commands to begin tracking keywords:</p>

<p><strong>follow "web 2.0" </strong></p>

<p>will track all references to "web 2.0" on Twitter. </p>

<p><strong>follow "web 2.0", "web 3.0"</strong></p>

<p>will track all references to "web 2.0" and "web 3.0"</p>

<h2>Will a Simplified Service Save Particls?</h2>

<p>For whatever reason, the original RSS tracking and alerting service provided by Particls never quite caught on. Perhaps it was just a little ahead of its time. The service aimed to help us address our RSS/information overload issues before some of us even had any <em>to</em> address. But the concept behind the service was solid: a desktop ticker, instant prioritized alerts, easy sharing of RSS items, simple feed subscriptions, and so on. In fact, <a href="http://www.readwriteweb.com/archives/particls_launches_advanced_alerts_platform.php">that version of Particls</a> sounds a lot like one of our favorite desktop apps today, <a href="http://www.readwriteweb.com/archives/snackr_is_an_rss_addicts_dream.php">Snackr</a>, which does many of the same things but launched nearly a year later. </p>

<p>We thought Particls 1.0 was a good first attempt at managing those sorts of issues, but it was not without its problems. The program was a Windows-only client, had some UI challenges, and, from personal experience, hit an older laptop's CPU just a bit too much. </p>

<p>Later, the company split the Particls solution into half, with one half becoming <a href="http://blog.engagd.com">Engagd</a>, an attention management engine, and the other half becoming Particls 2.0, the visualization and alerting engine. <a href="http://blog.particls.com/index.php/2009/02/introducing-the-particls-fountain/">From the sound of it</a>, those two projects have now been abandoned - the company notes that all resources have been diverted to the new project, Fountain.</p>

<h2>Oops, a DM Limit</h2>

<p>Unfortunately, there is one major concern regarding the new service, and it's not really Particls' fault. Currently, Twitter API limits direct messages to 5000 per day for whitelisted accounts. That will severely impact what the service can do using DMs. </p>

<p>Here's <a href="http://seesmic.com/videos/92B5hpICNq">a video of Chris</a> pondering this issue: </p>

<div style="padding-bottom: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; float: none; padding-top: 0px" id="scid:5737277B-5D6D-4f48-ABFC-DD9C333F4C5D:d44f8673-0133-42cf-a9de-6dfa7cb2955c" class="wlWriterEditableSmartContent"><object width='435' height='355'><param name='movie' value='http://seesmic.com/embeds/wrapper.swf'/><param name='bgcolor' value='#666666'/><param name='allowFullScreen' value='true'/><param name='allowScriptAccess' value='always'/><param name='flashVars' value='video=92B5hpICNq&amp;version=threadedplayer'/><embed src='http://seesmic.com/embeds/wrapper.swf' type='application/x-shockwave-flash' flashVars='video=92B5hpICNq&amp;version=threadedplayer' allowFullScreen='true' bgcolor='#666666' allowScriptAccess='always' width='435' height='355'></embed></object></div>

<p>This API limit is a clear example of the sort of thing a company would gladly pay Twitter for access to, if only there was the option. It's unfortunate that Twitter's hard-set limits are actually affecting the abilities of other companies to innovate around the core product. </p>

<p>Yet that won't stop them from trying. For the record, Particls is not the first service to attempt to implement the missing Twitter Track feature. For example, the Twitter toolkit from <a href="http://www.tweetlater.com/">TweetLater</a> also provides this functionality. However, the difference between the two services is that TweetLater provides tracking via an emailed digest - not real-time alerts as Particls does. </p>

<h2>Will Fountain be a Success?</h2>

<p>Whether Particls Fountain will succeed where previous incarnations did not is something that's yet to be seen. However, the company is now actively working with the community and letting them drive the development. This critical step is vital to making a successful product, so it's encouraging to see the interaction. </p>

<p>Through the <a href="http://particls.uservoice.com/">UserVoice site</a>, 100 or so testers have already begun providing feedback about Fountain. They - and you - will be the people voting on the next step for the service, whether that's <a href="http://particls.uservoice.com/pages/general/suggestions/114741-allow-me-to-see-my-history-of-alerts-on-the-website">tracking your alerts history on the web</a>, <a href="http://particls.uservoice.com/pages/general/suggestions/122375-email-digest">receiving an email digest</a>, <a href="http://particls.uservoice.com/pages/general/suggestions/114742-allow-me-to-view-and-adjust-my-topics-on-a-web-based-dash">adjusting alerts through a web-based dashboard</a>, or something else entirely.</p>

<p>If you want to give the service a try, you can do so today; just follow the <a href="http://blog.particls.com/index.php/instructions">instructions</a> above. Besides UserVoice, you can also give feedback directly to the creators of Particls on Twitter: just follow <a href="http://www.twitter.com/ashleyangell">@ashleyangell</a>, <a href="http://www.twitter.com/stephenkelly">@stephenkelly</a>, and <a href="http://www.twitter.com/chrissaad">@chrissaad</a>. </p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127574</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127574" />
    <title>Comment from ITrush on 2009-02-23</title>
    <author>
        <name>ITrush</name>
        <uri>http://www.itrush.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.itrush.com">
        <![CDATA[<p>This is very interesting.. thanks also for showing us example on how to setup Particls.</p>]]>
    </content>
    <published>2009-02-23T14:44:08Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127575</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127575" />
    <title>Comment from Zee on 2009-02-23</title>
    <author>
        <name>Zee</name>
        <uri>http://www.zee.me</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.zee.me">
        <![CDATA[<p>Gosh it has been a while...they still have Marshall writing for Techcrunch and Phil Butler writing for RWW! :)</p>]]>
    </content>
    <published>2009-02-23T14:49:55Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127577</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127577" />
    <title>Comment from Mario Valente on 2009-02-23</title>
    <author>
        <name>Mario Valente</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p></p>

<p>  If you want to replace "track" its easier if you<br />
 just use a client (like Twhirl) that has a search<br />
 feature (with persistence). I also use this to<br />
 "follow" people that I dont want to actually *follow*<br />
 ( from:x OR to:x) and get to see tweets addressed to<br />
 them as well :-)</p>

<p>  -- MV</p>]]>
    </content>
    <published>2009-02-23T15:10:58Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127580</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127580" />
    <title>Comment from Corvida on 2009-02-23</title>
    <author>
        <name>Corvida</name>
        <uri>http://friendfeed.com/corvida</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/corvida">
        <![CDATA[<p>I was wondering what happened to Particls. They were definitely ahead of their time.</p>]]>
    </content>
    <published>2009-02-23T15:11:40Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127578</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127578" />
    <title>Comment from Sarah Perez on 2009-02-23</title>
    <author>
        <name>Sarah Perez</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>@Mario: I agree that clients like Twhirl/TweetDeck/etc are great for when you're at your desktop, but given the IM option, you can "track" from anywhere - even your mobile phone.</p>]]>
    </content>
    <published>2009-02-23T15:15:07Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127581</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127581" />
    <title>Comment from Sarah Perez on 2009-02-23</title>
    <author>
        <name>Sarah Perez</name>
        <uri>http://friendfeed.com/sarahintampa</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/sarahintampa">
        <![CDATA[<p>@Corvida: Me too. I had high hopes for them at one time.</p>]]>
    </content>
    <published>2009-02-23T15:19:54Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127586</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127586" />
    <title>Comment from Craig Eddy on 2009-02-23</title>
    <author>
        <name>Craig Eddy</name>
        <uri>http://friendfeed.com/kregger</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/kregger">
        <![CDATA[<p>Interesting. I "signed up" for a few obscure work and business related terms just to see if any ever show up.</p>]]>
    </content>
    <published>2009-02-23T15:27:12Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127582</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127582" />
    <title>Comment from PXLated on 2009-02-23</title>
    <author>
        <name>PXLated</name>
        <uri>http://www.geise.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.geise.com">
        <![CDATA[<p>How does one then unfollow...is it...<br />
d particls unfollow "web-2.0"<br />
?</p>]]>
    </content>
    <published>2009-02-23T15:40:00Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127587</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127587" />
    <title>Comment from Ken Sheppardson on 2009-02-23</title>
    <author>
        <name>Ken Sheppardson</name>
        <uri>http://friendfeed.com/kshep</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/kshep">
        <![CDATA[<p>Track has been "back" since last July thanks to Dustin Sallings and Twitterspy. I wonder how Particls will get around the 20K/hr API call limit that's been giving Twitterspy fits lately.</p>]]>
    </content>
    <published>2009-02-23T15:49:07Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127590</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127590" />
    <title>Comment from Sarah Perez on 2009-02-23</title>
    <author>
        <name>Sarah Perez</name>
        <uri>http://friendfeed.com/sarahintampa</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/sarahintampa">
        <![CDATA[<p>@Ken: Twitterspy lets you use XMPP clients (http://www.techlifeweb.com/2008/07/07/how-to-set-up-twitterspy-in-google-talk/), but Particls also lets you use Twitter itself to track keywords - similar to the original Twitter track feature. I was not aware Twitterspy does this (I don't think it does?). Please let me know if I'm wrong.</p>]]>
    </content>
    <published>2009-02-23T15:53:44Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127591</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127591" />
    <title>Comment from Brian Roy on 2009-02-23</title>
    <author>
        <name>Brian Roy</name>
        <uri>http://friendfeed.com/briantroy</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/briantroy">
        <![CDATA[<p>It doesn't matter... there are severe API limits on DMs - we are all just dancing around the API barriers. Particls will either a) get Twitter to unlimit them for $$$ OR b) bounce off the API limits the same way TwitterSpy, justSignal, SocialToo, etc do.</p>]]>
    </content>
    <published>2009-02-23T15:56:48Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127593</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127593" />
    <title>Comment from Ken Sheppardson on 2009-02-23</title>
    <author>
        <name>Ken Sheppardson</name>
        <uri>http://friendfeed.com/kshep</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/kshep">
        <![CDATA[<p>Sarah: No, Twitterspy doesn't track via DM, although it'd be easy to add... if not for the fact that it's already hitting the API limit ceiling with ~900 users, and adding API calls to retrieve and send DMs would put it further into the red. If a DM interface is/was necessary for track to be declared "back", I guess you've got it now. I'm just a little jaded as every month or so there's been yet another service that gets promoted as the solution to the track problem, when they're certainly not the first.</p>]]>
    </content>
    <published>2009-02-23T16:11:25Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127594</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127594" />
    <title>Comment from Sarah Perez on 2009-02-23</title>
    <author>
        <name>Sarah Perez</name>
        <uri>http://friendfeed.com/sarahintampa</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/sarahintampa">
        <![CDATA[<p>@Ken I see. I have to say, though, this is the first solution I've been excited about thanks to Twitter DM integration. But as the article mentions, the API limits are a deal-breaker for everyone who tries to solve the Track problem.</p>]]>
    </content>
    <published>2009-02-23T16:14:00Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127595</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127595" />
    <title>Comment from Ken Sheppardson on 2009-02-23</title>
    <author>
        <name>Ken Sheppardson</name>
        <uri>http://friendfeed.com/kshep</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/kshep">
        <![CDATA[<p>Sarah: The article says "However, those who use an XMPP client will not have any issues." They will, if the service is at all successful. Twitter limits API calls to 20K/hr, so if each user is tracking one unique term, at 20K users you can only look for posts containing that term once an hour. That's not quite the "real time". There are ways to work around the limit, but you're basically "hacking" Twitter and working around their intent, which seems to be to prevent services like this from taking off.</p>]]>
    </content>
    <published>2009-02-23T16:18:28Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127596</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127596" />
    <title>Comment from Sarah Perez on 2009-02-23</title>
    <author>
        <name>Sarah Perez</name>
        <uri>http://friendfeed.com/sarahintampa</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/sarahintampa">
        <![CDATA[<p>@Ken: Aaaah, I see. I'll correct that now. Thanks for clarifying.</p>]]>
    </content>
    <published>2009-02-23T16:19:59Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127598</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127598" />
    <title>Comment from Ashley Angell on 2009-02-23</title>
    <author>
        <name>Ashley Angell</name>
        <uri>http://www.particls.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.particls.com">
        <![CDATA[<p>Hi everyone, Ashley here from the Particls team.</p>

<p>Please note that due to demand, the bot's autofollow feature is being flaky so it may not auto-follow you right away.</p>

<p>Don't forget to try the Gtalk bot as well, particls@particls.com</p>

<p>Thanks for the writeup - we hope Particls Fountain is useful to you.</p>

<p>We are still very interested in expanding this product to help users manage their attention across platforms, but we thought this time we would start small and let the community dictate features that get priority. To manage *our* Attention.</p>

<p>Feedback welcome!</p>

<p>Ash</p>]]>
    </content>
    <published>2009-02-23T16:45:55Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127599</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127599" />
    <title>Comment from Ken Sheppardson on 2009-02-23</title>
    <author>
        <name>Ken Sheppardson</name>
        <uri>http://friendfeed.com/kshep</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/kshep">
        <![CDATA[<p>BTW, Twitterspy is open source, so anybody is free to fire up their own instance, which would certainly be one way to avoid the API limit. Maybe somebody would like to see if they can implement DM before Dustin can, eh? :-) <a href="http://dustin.github.com/twitterspy/" rel="nofollow">http://dustin.github.com/twitterspy/</a></p>]]>
    </content>
    <published>2009-02-23T16:48:39Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127603</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127603" />
    <title>Comment from Julien on 2009-02-23</title>
    <author>
        <name>Julien</name>
        <uri>http://blog.notifixio.us</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.notifixio.us">
        <![CDATA[<p>@Sarah : @Ken has a point. Twitterspy deos pretty much the same!</p>

<p>Also, you could really do the same thing with Notifixious. Just Ctrl-C/Ctrl-V the URL of a Twitter search (Summize) page search result into notifixious...<br />
Example:  you can track "RWW" by pasting this url : <a href="http://search.twitter.com/search?q=RWW" rel="nofollow">http://search.twitter.com/search?q=RWW</a><br />
into <a href="http://notifixio.us" rel="nofollow">http://notifixio.us</a><br />
(I did it for you and you can subscribe at <a href="http://notifixio.us/sources/6331-search-twitter" rel="nofollow">http://notifixio.us/sources/6331-search-twitter</a> )</p>

<p>;)</p>]]>
    </content>
    <published>2009-02-23T17:24:42Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127607</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127607" />
    <title>Comment from Dustin Sallings on 2009-02-23</title>
    <author>
        <name>Dustin Sallings</name>
        <uri>http://friendfeed.com/dlsspy</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/dlsspy">
        <![CDATA[<p>Watching your DMs works. I don't think delivery via DM could work for any real life userbase.  Don't think of it as 20k users * 1 track == 1/hr.  Think 1000 users * 1 track * 20 matches == 1/hr.  Each individual delivery is now a scarce resource.</p>]]>
    </content>
    <published>2009-02-23T17:32:37Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13959-comment:127646</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13959" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/twitter_track_is_back_thanks_to_particls.php#c127646" />
    <title>Comment from Jason Salas on 2009-02-23</title>
    <author>
        <name>Jason Salas</name>
        <uri>http://friendfeed.com/jasonsalas</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://friendfeed.com/jasonsalas">
        <![CDATA[<p>I've been beta testing Particls for awhile and it's a great service.  The DM limitation is a pain, especially for noisy or excessively large topic clusters, but really neat otherwise.</p>]]>
    </content>
    <published>2009-02-24T05:07:25Z</published>
  </entry>

</feed>