After a number of users reported that their feeds weren’t being shortened by is.gd anymore, I talked to the people at is.gd, and they have introduced API limits which make using it with twitterfeed impossible. As is.gd doesn’t want to support the levels of API usage that twitterfeed creates, they have asked for is.gd to be removed from twitterfeed. All feeds that were previously using id.gd have been reset to use tinyurl, but you can of course log into twitterfeed and select a different shortener from the ones available.
Apologies for the inconvenience, but I’m only acting for is.gd, who want their API to be used only for low volume applications.
12 responses so far ↓
Fyre Vortex // January 2, 2009 at 1:48 pm |
No…! Is.Gd is awesome… Why did this happen…?
titanas // January 2, 2009 at 1:49 pm |
So, changing URL shortener preferences automatically resets all previously created URLs?
Daniel // January 2, 2009 at 1:51 pm |
:s
twitterfeed // January 2, 2009 at 1:52 pm |
Fyre Vortex – it’s just down to the level of API traffic. twitterfeed creates tens, perhaps hundreds of thousands requests a day, and is.gd don’t want to support this level, so have started to limit API use. Really not much I can do about this, it’s is.gd’s decision.
titanas – any existing post will not be affected, but any new twitterfeed posts will now use tinyurl, or (if you log in and edit your feed) whatever other URL shortener you want to use.
Fyre Vortex // January 2, 2009 at 3:21 pm |
We must start a petition!
pigsonthewing // January 9, 2009 at 5:14 pm |
is.gd doesn’t preserve #fragment identifiers (http://tinyurl.com/82cup3) – please only use shorteners which do.
Matt // February 2, 2009 at 12:58 am |
Aw, that sucks. is.gd just shot themselves in the foot by adding API limits.
Zoasterboy // February 21, 2009 at 2:15 am |
I’m assuming the way a shortened URL is requested on this site is all through the server. Can’t you just change it so all URL’s are requested through client side JavaScript, thus spreading the traffic out instead of it all coming from one IP? Or do they just not want lots of traffic period.
twitterfeed // February 25, 2009 at 12:00 am |
Zoasterboy – the way twitterfeed works, all processing is done server-side, so any client-side solution wouldn’t really work.
mariuz // April 13, 2009 at 3:22 pm |
could you add metamark.net ?
i see that is supported on identi.ca and maybe they allow a lot of requests
Ben Bonilla // July 24, 2009 at 6:08 am |
As a top Twitter business user, I was sent an advance copy of the Tweet Adder System for my review. This is by far the best Networking Tool I have used for Twitter!
diggma // October 18, 2009 at 12:06 pm |
We must start a petition!