Well, as many of you have pointed out, hashtags.org has been down since July 10th - nearly a month. This is because we rely on Twitter’s XMPP service to recieve tweets. They took the service down on the 10th and since then we’ve been waiting, patiently.
I have emailed the folks at twitter several times, but I haven’t been able to get a solution from them. In the mean time we are going to try a few other ways to get the data from them - even if it means banging on the public RSS feed every 2 seconds.
I assure you that we will be back, it’s just a matter of when Twitter gets it’s things in order.
comments:
12 Comments »
RSS feed for comments on this post. TrackBack URL
Personally I’d just get http://twitter.com/statuses/friends_timeline.xml?since_id=12345 until their server catches fire :-).
Comment by Matthias — August 13, 2008 @ 9:14 am
Did you see this message? http://groups.google.com/group/twitter-development-talk/msg/17960da644178dc9
There’s apparently an xml feed of the data available.
I’m also wondering where services like TweetScan are getting their data…
Comment by Damon — August 26, 2008 @ 4:06 am
Yes, c’mon! Just use their API like Matthias stated.
Comment by sprain — August 28, 2008 @ 8:32 am
Two months and counting. =(
Are there any alternatives to hashtags.org out there for this sort of thing for now. We have a code camp coming up soon and we were counting on using hashtags with twitter.
Comment by vanriper — September 22, 2008 @ 12:25 am
Any updates?
Comment by Scott K — September 24, 2008 @ 11:28 pm
Just use search.twitter.com
Comment by Alex — October 2, 2008 @ 6:29 pm
Could you just poll the primary RSS feed? It would have a minute lag, but much better than a 3 month+ lag.
Not sure if Twitter limits that or no, but sure would be nice to have HashTags back up and running.
Comment by Benjamin — October 7, 2008 @ 8:07 am
Looks like Twitter’s answered the XMPP question: http://status.twitter.com/post/53978711/im-not-coming-soon
Maybe parsing the public feed or the @hashtags feed would do the trick. I believe that’s kosher and cached at their servers ever 60 seconds. Delays would be only a minute in length that way.
I’m new to the Twitter Terms of Service, so you may know better.
Would love to see you return.
Comment by Benjamin — October 10, 2008 @ 2:07 pm
Sounds like a job for Gnip!
Comment by Ben Godfrey — October 14, 2008 @ 5:06 am
Why don’t you use Gnip? They have a publisher for XMPP with a Twitter feed.
Comment by Daniel W. Crompton — October 19, 2008 @ 6:12 pm
Come on! What’s the go?
Comment by Nikki — October 23, 2008 @ 5:58 am
Looks like Hashtags is back. If whatever solution you’re using now is unsatisfactory, try asking the folks at FriendFeed how they get their Twitter data.
Comment by Voyagerfan5761 — December 5, 2008 @ 2:02 am