All–
I’m very sorry that Twitter Tools is not currently working. The breakage appears to be due to an issue on the Twitter side.
Thank you kindly for your patience while things get straightened out.
Your friend,
–Alex King
PS. Thank you to those of you went to the forums as requested, I’m sure you already found this information posted there.
Thanks Alex for the update! After I sent you an e-mail about this, THEN I checked your blog. You are obviously aware of the issue and it does seem like Twitter did something on their side to break your awesome Twitter Tools.
Again, thanks for keeping us in the loop. As long as you know about it, that’s good enough for me.
Hi Alex,
we had an outage last night in our caching infrastructure. We thankfully didn’t lose any updates, but those made between ~3 AM PST and ~10 AM PST were not deliveried to IM or SMS, and won’t appear on the first page of updates for a given user.
Sorry for any inconvenience!
Blaine
Hi Blaine–
Thanks for taking the time to stop by and comment here. I believe what the Twitter Tools users are experiencing is the 301 error discussed in the Google Groups thread linked in the post above.
The 301 location given is the same as the requested location:
http://twitter.com/s[...]imeline.json
Hope this helps.
[...] is not an issue in Alex’s code, as he points out in a recent blog post. This is an issue with Twitter’s infrastructure, which users are noticing more as the service [...]
Alex,
I’ve just resolved the 301 issue. I no longer see any redirects for requests from your API client in the logs.
The issue was related to the request filter in front of our application.
Requests with twitter.com in the HTTP host: header were working fine, but host:twitter.com:80 was inducing a 301.
We’ve modified our filter to account for this. My apologies for not catching it sooner!
Jeremy
Hi Alex,
Just in time to release a needless patch! Heh. Oh well, I wanted to learn more about WordPress’ development environment for plugins. In case you’re interested, I put a patch up that utilizes CURL when available. You can find the link in my post: http://joshuahoover.[...]-plugin-fix/
Funny that I just finished writing that post and Jeremy announces that they fixed it on their end. I figured they would sooner or later, but it gave me an excuse in the mean time to learn more about WordPress plugin development.
Keep up the great work with the plugins!
Josh
Awesome job guys. Thank you Alex for updating us on this and thanks to Twitter and staff for fixing it.
The logon error I had is gone and it now says successful as I used to.. so it’s back to Tweets with Twitter and Twitter Tools.
Hi Alex-
Your Twitter plug-in looks fantastic, but currently I use Jaiku. Any chance of encouraging you to make the same type of plug-in for Jaiku? I’m willing to donate! Give me an idea of how much of a donation we’d need to raiser to convince you to work on a Jaiku version.
Alex, do you work for twitter or something?
I have little interest in Jaiku (or Pownce), so while a port of Twitter Tools to those platforms is not likely to be challenging technically, it’s going to need to be a fully funded Crowd Favorite development project to get done (or someone else can do it) since it isn’t something I’m likely to make time for.
Okay… thanks for reply. I like Twitter, but there’s just something about Jaiku I like better. Not sure what. Also the Twitter badges were not updating on my blog when I tried them out. Some people have told me that Twitter can be fairly unreliable at times.
If I knew more about code I’d try to covert Twitter Tools myself.
P.S. Would you be interested in taking the part of Twitter Tools that creates a daily digest post and creating a separate plug-in from it that could work with any RSS feed? Would donations to the cause help?
Just found this thread, sorry about the earlier comment on Twitter Tools. Am using the excellent Macro plugin and will drop a payment via PayPal tomorrow. Mahalo