Users are accustomed to the fact that use of *free* services is entirely *as is* and at their own risk, so none of us should feel we have to protect their privacy or their security beyond this original expectation. If they don't like the performance, security, or privacy implications of this change, they'll leave Twitter, just like they left Facebook. But that is ultimately Twitter's responsibility to control and react to. Our responsibility is to keep rowing collectively in the same direction, or get off the boat. :)
On Jun 9, 10:17 am, Harshad RJ <[email protected]> wrote: > On Wed, Jun 9, 2010 at 6:48 PM, Dewald Pretorius <[email protected]> wrote: > > > I don't buy the click tracking privacy argument. Twitter will have no > > more insight into clicks than what bit.ly or any other shortening > > service has, > > The difference being that the user who clicks the links in Twitter will have > most probably logged into Twitter. Thus, Twitter can directly associate a > click with a user. > > When clicking on bit.ly shortened URLs it is very very unlikely that the > user is logged into bit.ly. That is because only people who shorten URLs > need a bit.ly account (which is a very small percentage). > > -- > Harshad RJhttp://hrj.wikidot.com
