[twitter-dev] Re: RESTful API to unshorten URL's from twitter
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 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 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 wrote: > > > On Wed, Mar 4, 2009 at 12:38 PM, Nick Halstead > >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
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
Only 1 in 10 tweets tends to have a link - so you would need to receive 1000 tweets in an hour (on average) to run out of requests - but I guess that is a possability, we are at very early stages but we will look at upping to maybe 200 an hour and see how it goes. On Mar 5, 9:49 pm, Ed Finkler wrote: > This is a cool feature, Nick. I appreciate you opening it up to the > community. > > One concern I have, as a desktop app developer, is that a user could > probably plow through 100 reqs/hr pretty easily if they're following > 1000 or more users. Now one might say "most people don't follow that > many people, so you're an idiot," and they'd be right. I happen to > follow that many, though, so I'd notice it 8). Also, people who are > essentially edge cases when it comes to # of folks they follow also > tend to bitch the most. Like me. > > Right now I'm doing url un-shortening in the client, but I would look > seriously at using your service if the limits were a bit higher. > > -- > Ed Finklerhttp://funkatron.com > Twitter:@funkatron > AIM: funka7ron > ICQ: 3922133 > XMPP:funkat...@gmail.com > > On Mar 4, 3:38 pm, Nick Halstead wrote: > > > Today we launched an API for tweetmeme, for those who havent tried it, > > we aggregate all the twitter URL's to rank the most popular stories. > > Well the upside of this is that we have massive database of all the > > short URL's - and where they resolve to, included in this we also go > > and grab the page that it points at, and so we fetch the title, > > category of content, and a few other bits. > > > 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. > > > Would love to get feedback on what other data mining methods we could > > expose.
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
Hi Adam, What was the request? the error looks more like a problem with your client fetching rather than with our side - the API has had zero downtime, just check an example link e.g. http://api.tweetmeme.com/url_info?url=http://tinyurl.com/cdngq8 On Mar 5, 2:03 pm, Adam <1ju...@googlemail.com> wrote: > On Mar 5, 8:30 am, Nick Halstead 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. > > Hi Nick, > > I'm struggling to even connect to your API. This is the error I get: > > msxml3.dll error 'c00ce56e' > System error: -1072896658. > > Any ideas? > > Adam
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
This is a cool feature, Nick. I appreciate you opening it up to the community. One concern I have, as a desktop app developer, is that a user could probably plow through 100 reqs/hr pretty easily if they're following 1000 or more users. Now one might say "most people don't follow that many people, so you're an idiot," and they'd be right. I happen to follow that many, though, so I'd notice it 8). Also, people who are essentially edge cases when it comes to # of folks they follow also tend to bitch the most. Like me. Right now I'm doing url un-shortening in the client, but I would look seriously at using your service if the limits were a bit higher. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Mar 4, 3:38 pm, Nick Halstead wrote: > Today we launched an API for tweetmeme, for those who havent tried it, > we aggregate all the twitter URL's to rank the most popular stories. > Well the upside of this is that we have massive database of all the > short URL's - and where they resolve to, included in this we also go > and grab the page that it points at, and so we fetch the title, > category of content, and a few other bits. > > 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. > > Would love to get feedback on what other data mining methods we could > expose.
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
Hey, I also run a service specifically dealing with lengthening short urls (http://www.longurlplease.com), it's api has proven to be robust, easily handling 100's of thousands of api calls per day, thanks app engine ;) Right now all it does is return the long url - but I've plans, amongst other things to give information such as page title. Hope you find it useful. I'd love your feedback. Cheers, Darragh Curran On Mar 5, 2:03 pm, Adam <1ju...@googlemail.com> wrote: > On Mar 5, 8:30 am, Nick Halstead 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. > > Hi Nick, > > I'm struggling to even connect to your API. This is the error I get: > > msxml3.dll error 'c00ce56e' > System error: -1072896658. > > Any ideas? > > Adam
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
On Mar 5, 8:30 am, Nick Halstead 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. Hi Nick, I'm struggling to even connect to your API. This is the error I get: msxml3.dll error 'c00ce56e' System error: -1072896658. Any ideas? Adam
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
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, Santosh www.Twitblogs.com Twitter :- http://twitter.com/santoshpanda On Thu, Mar 5, 2009 at 8:30 AM, Nick Halstead 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 wrote: > > On Wed, Mar 4, 2009 at 12:38 PM, Nick Halstead >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 >
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
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 wrote: > On Wed, Mar 4, 2009 at 12:38 PM, Nick Halstead 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
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
We have already implmented Tweetmeme's API in our test site and will pish it live on Friday. Good job Nick. Thanks in advance Sam www.twitblogs.com/ssethi This email is: [ ] bloggable [ ] twittable [ ] ask first [X] private Sent from: Poplar Eng United Kingdom. 2009/3/4 Nick Halstead https://www.linkedin.com/addcontacts?addresses=nickhalst...@gmail.com&addByHand=Add+these+contacts&batchID=0&context=0&membersOnly=true¤tPage=1&goback=.oca_1_false_0_0> > > > Today we launched an API for tweetmeme, for those who havent tried it, > we aggregate all the twitter URL's to rank the most popular stories. > Well the upside of this is that we have massive database of all the > short URL's - and where they resolve to, included in this we also go > and grab the page that it points at, and so we fetch the title, > category of content, and a few other bits. > > 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. > > Would love to get feedback on what other data mining methods we could > expose. >
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
Nick Halstead wrote: Today we launched an API for tweetmeme, for those who havent tried it, we aggregate all the twitter URL's to rank the most popular stories. Well the upside of this is that we have massive database of all the short URL's - and where they resolve to, included in this we also go and grab the page that it points at, and so we fetch the title, category of content, and a few other bits. 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. Would love to get feedback on what other data mining methods we could expose. It is pretty cool. I don't want to be a pain, but story is not written storie: http://api.tweetmeme.com/popular.xml - pain to fix this one though if you already have published the api.
[twitter-dev] Re: RESTful API to unshorten URL's from twitter
On Wed, Mar 4, 2009 at 12:38 PM, Nick Halstead 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
