UPDATE: As of late Tuesday August 16, some apps, notably HootSuite, have begun fixing this problem.
You may have begun noticing many Tweets with links that are missing the http:// and that are NOT clickable. This is not strictly due to some Twitter bug, it is because people and applications have not yet adapted to Twitter’s new way of displaying URLs.
Because Twitter now removes the http:// from links, if you use a method that copies one tweet into another (such as to prepare to retweet with a comment) you have to type in the http:// by hand yourself.
What the problem is
Much of the time, URLs now display without an http:// visible, but ARE still clickable. However, many people have been copying what is displayed in one tweet into another (some apps do this for you automatically, and will need to update their method). This results in tweets that both have no http:// and are NOT clickable.
Most apps that use “classic” retweet so as to allow you comment simply copy the text of one tweet into a new Tweet, adding only some retweet syntax (such as “RT @user: …”).
What changes to expect
This is a huge problem. It’s hard for an app to figure out where to add the http:// now that most tweets don’t display it. So don’t count on your favorite app solving the problem right away. There are a couple of approaches they could take, but I suspect the developers now in communication with Twitter about the problem will figure out a standard solution soon.
What you can do now
Whether you or your app copied a tweet into another tweet, use the “copy link” function of your browser (here’s how) to grab the link from the source tweet if you don’t want to manually type in the http:// yourself.
However, in some cases copying the text of the link will give you a full URL that begins with http://t.co/… If so, you won’t have to add the http:// yourself.
If you want to copy the exact text, but are getting a t.co link that you don’t want (maybe you want to keep the analytics of a different URL service) copy both some text above and below the tweet that you want to copy from. This will bypass your browser’s attempt to put the hidden t.co link onto your clipboard when you copy.
Why Twitter has made this change
Twitter has begun to take every URL shared on Twitter and convert it into a t.co link through Twitter’s infrastructure. Twitter’s t.co URL wrapper now “wraps” all URLs 19 characters long and greater.
Twitter’s URL simply redirects to whatever URL was used, so, for example, if you use an URL that gives you analytics, you still get them. But now your referer is t.co—e.g. it shows up in Google Analytics as “t.co / referral”) The actual website is checked against a list of harmful sites, so that bad links can be blocked before you get a chance to click on them. This also gives Twitter detailed information on how links are used and clicked on that they can use in many ways.


{ 22 comments… read them below or add one }
Twitter should follow the standard for URL – and not expect other to”adapted to Twitter’s new way of displaying URLs”. Twitter looks more and more like a legacy.
As for the Twitter’s t.co URL wrapper and “checked against a list of harmful sites, so that bad links can be blocked before you get a chance to click on them” this is nonsense.
A browser does this for you.
Redirection of URL is problematic – and Twitter does this for one simple reason:
Datamining and profiling.
I don’t find in your privacy-statement that you track cross sites (who clicked what t.co and so on). Can you please point me to the information regarding this.
Beside the obvious privacy issues, it does not function properly. as every so often the t.co replacement for a proper URL does not resolve.
Would you fix twitter for me please ! I cannot tweet but I can read time line ;( (-,-?
#thaiflood ;”(
Try http://bit.ly/QuickTwitterFix
fix twitter for me please
What problem are you having?
Hi Dave, it’s a lot of work just to give someone credit for an RT yet preserve the link in the tweet. I’m using Buffer (bit.ly) or Timely (awe.sm) and I’m confident that I miss seeing lot of retweets because of this.
I also noticed that the counts displayed on the Tweet button on my blog were incorrect for the last few days – but I checked just now and they appear to be more accurate now.
Thanks for the details.
►Correction – the tweet counts from the tweet button are still wrong on my blog. (Earlier I was looking at the comment count by mistake.)
Sorry to hear that! Twitter is still in the midst of some major support issues, so I would suggest reporting your issue via http://bit.ly/TWICKET .
Dave that’s an interesting find and I realized this problem when I was using Hootsuite. And today one of my friend (Kim) shared this article and then I realize what the problem is. Hopefully all 2rd party twitter client will soon adopt this new link style and this won’t be problem anymore..!!
Good work!
Hopefully!
you’re referer?…your*
Thanks! More of a lazy typing problem than a misunderstanding…but a typo nonetheless! Fixed
Google and Facebook have been in on the spying game for a long time; guess Twitter got jealous and decided that it had to monetize spying in the same way.
So does this mean that when we use bit.ly to shorten links then twitter revises those links that we will not recieve the data info like number of clicks etc from our links thru bit.ly? I use those click counters as research for the marketing department
You still get the data, but now the referer is t.co. I’ve updated the blog to make this clearer.
You’ll get your info just as before. What is happening is that everything is run through another process before being posted.
What is annoying me is mostly lately is that urls that is short in themselves like my own randomly is shortened as well
T.co is gay, Twitter should get rid of it soon.
This is just one of the things that is making #NewTwitter a less effective tool.
It’s certainly the biggest process I’ve ever seen Twitter break for users.
The Twitter API actually sends through the tweets URLs separately, so its pretty straight forward to find the links inside the tweet to make relevant changes as long as Twitter recognises the URL in the first place.
True to a point. The text URL in the tweet still has to be modified, and finding it in another part of the stream means matching it up to the tweet. The process is not quite trivial for an app to implement.
What’s annoying is that the http:// still count toward the 140, even though they don’t appear in the posted tweet.
Yes, that hasn’t changed, except for tricks like this 152-character tweet.
{ 3 trackbacks }