Twitter’s Latest API Changes Disable Gridjit (for now)
May 31st, 2008According to a recent thread on Twitter’s API discussion forum, they have decided to disable an API method that Gridjit relies on in order to provide its service. This is due to the scaling / load problems that Twitter has experienced in the last few months.
It is odd that they decided to remove the method if nobody was using (as they seem to conclude from the messages on the forum) and it wasn’t causing any problems for them. Obviously this isn’t the case for Gridjit.
In the short term, Gridjit is essentially unusable, and for that I apologize. Very soon, however, I will be releasing a new version of Gridjit that gets around this limitation.
Twitter, in this decision, however, has removed a very valuable part of their network - the discoverable, open nature of the platform. This, in my opinion, was a key differentiator for them from FriendFeed (which Gridjit 2.0 will also support). I do hope they change their minds. If you agree, please consider dropping them a line and asking them to re-enable the support for this method.
June 2nd, 2008 at 7:01 am
With Twitter, I use different tools for different things. These latest developments are crippling power users. I know the API is out of your hands but I’m looking forward to the return of Gridjit. For me it is part of my Ultimate Twitter Client arsenal along with IM which, sadly, has also been down for the last week.
June 2nd, 2008 at 7:05 am
I’m sorry to hear that you were also affected by this. Thank you for using and supporting Twitter through your blog. The next Gridjit is going to be very exciting (I hope). Thanks for staying tuned!
July 14th, 2008 at 2:05 am
[…] significantly enhanced in the last few months. I was planning an Alpha release for this summer when Twitter disabled a very important feature of their API with little warning, rendering the then current version of Gridjit completely useless. Within a few […]