Topic on Talk:Facebook

This is a permanent link to the first version of this post. You can view later versions on the post history page.

As I said to you in IRC (this is really for other people's benefit), a lot of the issue of embedding share buttons is that you're enabling tracking of those users. It's like giving CheckUser to Facebook's employees.

Most of the best ways to get around it require 2-click loading of the sharing widgets -- that is, not loading the JS until a positive action from the user indicates intent to share information with an external site. And then having it globally disableable with a gadget toggle, or a cookie for not-logged-in users. It's not trivial to implement something like that without harming user privacy, because the whole point of those facebook/stumbleupon/google+/digg/linkedin badges is to invade user privacy throughout the web. You have to subvert its functionality by sandboxing it, and wrapping it in JS.