News for hackers. Stuff that matters.
Re:When is a URL shortener not a URL shortener? by albedoa on Tuesday August 16, 2011 @09:16AM (#2890996)
A solution to this would be for Twitter to post the t.co URL if the original URL is longer than the t.co URL or if the original URL is too long to fit in the tweet. Else, it would display the original URL but direct it to the t.co URL for tracking.

So a tweet that says:

    Check it out: http://zombo.com
Would be posted as:

    Check it out: <a href="http://t.co/whatever">http://zombo.com</a>
This would preserve Twitter's tracking while maximizing the amount of information in the displayed URL as well as meeting the user's expectations, intent, and needs. Thoughts?
Re:When is a URL shortener not a URL shortener? by corin_ on Tuesday August 16, 2011 @10:03AM (#2891162)
That's what they already do through their web interface. And for any apps/whatever using the API, they give both version of the URL so that developers can do the same thing.
Re:When is a URL shortener not a URL shortener? by Pyrodogg on Tuesday August 16, 2011 @09:58AM (#2891143)
I was in the middle of writing a response say that would be "bait-and-switchy" until I remember we're already talking about URL redirection.

As long as it doesn't slow down the user experience much, adding in the additional layer, I think it'd be fine.