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
> t
Yes. I use the API to lengthen t.co links (and also bit.ly links using
their API)
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 l
It's a certain level of control which Twitter gets. If a spammy
application gets to Twitter, they can simply block those URLs via their
URL shortener. This is a level of spam control they don't get with
bit.ly, etc.
I'd like to point out that the API returns full URLs and all official
Twitter
Agreed : further absolutely unnecessary obfuscation of links.
The whole reason for the use of shorteners and even the 140 character limit
was in place due to the character restrictions on SMS. SO: Why not JUST
shorten these links for SMS messages they send out?? I'm sure SMS only
users are in a v
You can't with web intents and I believe that soon all links will be
t.co links. Basically, live with it.
If a bit.ly link gets wrapped in a t.co link, people will see the bit.ly
link, not the t.co link, except for some clients which don't implement
t.co links yet.
Get used to it.
Tom
On
