I think it pretty much depends on what Twitter will require us to do when following t.co links. On their own website and in their own Twitter clients I could imagine that they will track link usage from people clicking on the link (sooner or later.)
If they don't require third party clients to send any user related info when accessing t.co links, they only have the IP and possibly the user agent header. Cheers, ole @ mobileways.de / @janole on Twitter On 9 Jun., 15:30, "Brian Smith" <[email protected]> wrote: > Dewald Pretorius wrote: > > StatusNet, blog, etc.). If the privacy argument carried any water, then > bit.ly > > would be a far greater privacy threat than Twitter. > > I agree, and that's why I (and others) were working on solutions to get > around bit.ly and other link shorteners. And, Twitter has already developed > the ultimate solution to that privacy issue, but they just are refusing to > let API developers use it. That is what is so incredibly frustrating. > > Regards, > Brian
