Right now I prefer that the link is direct - if we wish to track (globally) then we could go via our own shortened URL which we will look into.
On Mar 5, 9:34 am, Santosh Panda <panda.sant...@gmail.com> wrote: > Hi Nick, > Good stuff! We are ready to launch Tweetmeme popular tweets with Twitblogs. > Btw the story URL points to the source of the story, I was under impression > that user will be redirected to Tweetmeme to ready the full story? > > Thanks, > Santoshwww.Twitblogs.com > > Twitter :-http://twitter.com/santoshpanda > > On Thu, Mar 5, 2009 at 8:30 AM, Nick Halstead <nickhalst...@gmail.com>wrote: > > > > > We have every single short url + long url that is posted on twitter, > > we take the whole firehose, there are outages at times with the > > firehose so sometimes we still miss bits, but coverage is very high. > > > On Mar 4, 8:51 pm, Nick Arnett <nick.arn...@gmail.com> wrote: > > > On Wed, Mar 4, 2009 at 12:38 PM, Nick Halstead <nickhalst...@gmail.com > > >wrote: > > > > > We have tried to stick very closely to the RESTful + twitter style > > > > API > > > > > The documentation is here ->http://www.tweetmeme.com/apidoc.php > > > > > An example of the url fetcher -> > > > >http://api.tweetmeme.com/url_info?url=http://is.gd/lznv > > > > > We also have two methods that let you fetch the most popular + the > > > > most recent stories. > > > > Cool... I'm doing the same kind of thing, but instead of trying to do it > > > comprehensively, I'm relying on predictive modeling and social network > > > analysis to minimize the data. I'm able to identify most, if not all, of > > > the popular URLs by making a system that is smart about who to track and > > how > > > often. > > > > How comprehensive is your data? Are you trying to do the entire > > firehose? > > > > > Would love to get feedback on what other data mining methods we could > > > > expose. > > > > By offering the API, you'll make it much easier for people to build on > > top > > > of it. Maybe the best thing you could do is to make that service as > > > complete and robust as possible. > > > > I think the future of things like this are in vertical-ization and > > > personalization. > > > > Nick
