Ns_bindin_aborted Jquery Post

Twitter liest mit!

http://abmahnwahn-dreipage.de/Abmahnung_Wissen.pdf Yesterday, shortly before midnight Twitter provided a striking example of what happens when the back-translation of short URLs fails: The links are dead! A potential worst case scenario for a company which relies on the continuous functioning of these short URLs. Nevertheless, this error also reveals some less nice internals of Twitter. But first things first. I wanted a short URL from a Tweet of the Pirate Party follow Pirate Party in local elections Telgte - ballots ended up in the shredder: http://is.gd/2LToV # T either

2 minutes ago from web

and landed at the following error message:

This error message appeared on all tweets and all service providers for short URLs, even with the Twitter partners
Bit.ly

. What is remarkable about this error message is now twofold:

Service providers for short URLs functioned properly, because you copied the URL out of the tweets and pasted them directly into the browser, the short URL resolve error. Also on the command line was easy to determine, for example, with curl-Is

, the objective of the short URL.

The URL that the error message triggers: http://twitter.com/link_click_count?url=http% 3A% 2F% 2Fis.gd% 2F2LToV & link = & type = web tweetId authenticity_token 3697982903 & userId = 56075977 & = b59b6d07e248ef735c6a404e15bc4f554475ee8c

1. If you look closer at this URL parameters fall link_click_count
,
2. tweetId

   and

   userId
eye. In other words, Twitter is not only just the clicks, but also create well (pretty much meaningless) user profiles, because why else would both Tweet, and user ID are recorded at every click. Technically, this is not necessary anyway. Thus, some questions which arise immediately Twitter beantworten sollte:

Was passiert mit den gespeicherten Daten?
Wie lange werden sie gepseichert?
Für welche Zwecke werden sie eingesetzt?
An wen werden sie weitergeleitet?