Twitterfeed users who haven’t specified a preference for a particular URL-shortener will notice that instead of using tinyurl as our default shortener, we are using bit.ly. There are a number of reasons why we believe this change will benefit all our users:
Greater stability: Bit.ly has taken great pains to have a stable service, building in multiple layers of redundancy so that bit.ly short urls can always resolve to their destination pages. Twitter recently also moved to bit.ly as its default and it made sense for Twitterfeed to also use the market-leader in this space.
Rich Analytics: Making bit.ly the default also means that Twitterfeed users can access bit.ly analytics and get far more information about what is happening to their posts once they are fed to Twitter. We’ll be working closely with the bit.ly team to develop richer analytics that give you the information you need to optimize how you interact with Twitter.
If for some reason, you would rather use another url-shortener you can still use the service of your choice, simply by changing your settings. However, we would strongly recommend that you use bit.ly to get the most out of Twitterfeed as we go forward.
Survey Winner
We’d also like to thank all of you who participated in our survey. We greatly appreciated your feedback and have chosen a random winner for the Amazon certificate: @cupcakeartist
Congrats! We’ll be getting in touch to deliver your prize.
35 responses so far ↓
Dan // July 15, 2009 at 11:30 pm |
Good choice. bit.ly has been my favourite for a while, but as soon as support for su.pr is added I’ll be switching to that.
Danica // July 16, 2009 at 4:39 am |
Meh, I don’t mind. I was already using bit.ly as my default URL shortener.
Jimbalaya // July 16, 2009 at 3:16 pm |
I agree with Dan, above … http://su.pr is the best URL shortening service I’ve used so far.
Staci J. Shelton // July 17, 2009 at 3:08 am |
Will we be able to integrate our own Bit.ly credentials so that our links are tracked under our own accounts? That would be AWESOME!
Thanks for such a fantastic service!
daverein // July 17, 2009 at 2:06 pm |
Satci – you already can. Under advanced options enter you bit.ly username and API key.
Troy // July 19, 2009 at 6:02 am |
Need to take a look at this this is big and can change your life so take a look
Bob // July 19, 2009 at 5:07 pm |
Hi
Do I need to have an API key? and API login? If so, where do i find it in my bit.ly account?
daverein // July 19, 2009 at 10:25 pm |
Bob – yes and yes but it’s easy enough to come by. The API login is your login username. The API key can be found by clicking on “Account” (once you’re logged in, top right hand corner) and it should be on display then.
http://davereinhardt.wordpress.com
Matt // July 20, 2009 at 6:05 am |
Awesome…but i’m also eagerly awaiting support for su.pr. Seems to be head and shoulders above the alternatives.
Alain-Christian // July 21, 2009 at 11:45 pm |
You do good work, Mario! Keep it up!
bit.ly - La brevità della rete « il Blog di Phcinque // July 24, 2009 at 5:14 pm |
[...] motivi (tratti dall‘introduzione a Bit.ly di [...]
Webfortis // July 28, 2009 at 10:48 pm |
When I try to use this as my default I get the follwoing error. “Error calling feedburner awareness API…” Any suggestions?
Seva Lapsha // August 12, 2009 at 9:36 am |
Why tr.im was removed from the list of shorteners???
Very sad.
David // August 12, 2009 at 1:53 pm |
tr.im stopped it’s service on Monday and restarted yesterday again. So tr.im should be back on the list
devilsoulblack // August 12, 2009 at 7:14 pm |
tr.im still ist not on the list
StFrancisIndy // August 13, 2009 at 8:23 pm |
Unfortunately this won’t work as a solution for us, as our IT people have blocked bit.ly. In addition, my login is no longer working so I can’t disable or update the shortener. Please contact me about how I can take care of this. We are getting quite a number of calls from disatisfied staff.
Gabi Aldamiz-echevarrÃa // August 14, 2009 at 2:32 pm |
Thanks @daverein I came here looking for the same thing:)
johndburger // August 16, 2009 at 5:32 am |
Another voice for reinstating tr.im, please.
Anything to break the Twitter/bit.ly hegemony.
Neil Ferree // August 22, 2009 at 4:52 am |
I hope you guys will NOT succumb to the masses and remain in the Bit.ly camp! For many of the sound reasons you reference in this post, Bit.ly (while it could be better) is far and away the best URL shortening service provider on the street.
joshua // September 7, 2009 at 12:12 am |
This program is great i just added my blog
http://dailycashsaver.blogspot.com/ and im getting twitter traffic and updates from twitter it is great!
JNFerree // September 7, 2009 at 5:21 pm |
I am also a big fan of bit.ly, so much so that I did a quick video and blog post on how to connect your Twitter and Facebook accounts to the bit.ly sidebar java applet so you can post good stuff to both accounts in 3 mouse clicks.
The link to the post is http://bit.ly/hBle and the link to the YT video is http://bit.ly/BitLy-Tip
lyrix // September 9, 2009 at 5:14 am |
Does it make sense to build our shorten URL with the same domain where our main app is located? Or twitterfeed will use one of the shorten service regardless how short the URLs already are?
I think it will add visibility to our site and help search engine find our site if the short URL use our own domain.
Not sure what we could be missing if we decide to go this route.
Affiliate link cloaking with Wordpress // September 11, 2009 at 6:57 pm |
[...] Looking forward to hear from you. Regards, Richard Richard – this might help. 1. Install the Bit.Ly sidebar applet w/ Firefox (or) 2. Try Scrnch.Me (or) 3. Check-out a 1/2 dozen Cloaked Affiliate Links I made w/ [...]
Yacine // September 16, 2009 at 9:25 pm |
Mario — First off BRAVO! for this app, great stuff!
Question: One of my feeds is using tinyurl despite my setting up bit.ly several times. Others are working fine. Any tips?
Also, seems the website is constantly very slow when opening pages to edit, create feeds or moving from page to page? I’m in California anything to do with it?
Thanks
@fastake
punktab // September 19, 2009 at 1:33 pm |
http://tr.im support would be highly appreciated.
Swzmaster // September 21, 2009 at 7:57 pm |
bit.ly is great choice for stats.
drakedalfa // October 5, 2009 at 9:30 pm |
Please add support for tr.im again
AAH // October 7, 2009 at 4:51 pm |
We have a fairly shotr URL as it is, so TwitterFeed (or maybe it’s twitter itself?) doesn’t convert our links to bit.ly ones… which means the really useful tracking isn’t available.
Might a feature be added to force all links to bit.ly?
Yacine // October 7, 2009 at 4:59 pm |
Yep same problem here: defaults to tinyurl instead of bit.ly. Had to stop using twitterfeed for now
Other issue was that every click takes any screen forever to load. Anyone has this issue?
Brittany // October 15, 2009 at 8:48 pm |
Su.pr would be great to add, too.
Saffa' // October 25, 2009 at 4:26 pm |
beside snipurl.com, I use a snipr.com. It’s a great too
rav // October 26, 2009 at 1:57 pm |
It’s a great. Thanks for added twitter feed in my blogs. ::
http://rakyumi.blogspot.com
dallasgoogleguru // November 15, 2009 at 9:45 pm |
You guys are doing a great job! Keep it up! Working on setting up some feeds for an attorney and I am impressed how easy it is!
dherold // November 16, 2009 at 10:14 pm |
I liked the bit.ly service, but now twitterfeed is defaulting to tinyurl for me. Can’t really continue with that …
Free Twitter Buttons // November 21, 2009 at 9:42 am |
I was using tiny url might need to was going to move anyway to bit.ly