On Jun 10, 2011, at 1:21 PM, Kosso wrote: > The massive trouble I have with all this is that I like to know what the > hell I'm clicking on before clicking a link. > It's kind of my right as a citizen of the web. > > I personally can't stand it when, for example a link fires up iTunes or goes > to some site I don't want to waste (possibly mobile and limited) bandwidth > on. I like to choose WHO I give MY visit/traffic to.
To be clear, the API returns all the information for all clients to display the original short URL, and navigate via t.co. We also look up the full destination URL and return that too, allowing even clearer navigation of where you as a user will end up when following a link. You can see this implemented on twitter.com today: https://twitter.com/joshtpm/status/79283124747501568 * The URL destination points to t.co * The displayed text of the URL is a cropped and shortened version of the real URL * The title (tooltip) of the URL displays the full address of the destination. I've further illustrated it with a screenshot here: https://skitch.com/benward/frff8/ The documentation for the URL entities that provide all of this information in the API response is here: http://dev.twitter.com/pages/tweet_entities Ben -- Platform Developer, Twitter -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
