4 ms·
Sorry, I should have made that more clear. Facebook knows about it. To get the plug-in, the browser has to hit the Facebook servers so all the context has alrea
by TheSandyWalsh 16y ago
Sorry, I should have made that more clear. Facebook knows about it. To get the plug-in, the browser has to hit the Facebook servers so all the context has already been passed along. I will edit. Thanks.
- brown9-2 16y agoThanks. The Facebook FAQ seems contradictory about this: 1) "Social plugins are engineered in such a way that no personal information is shared with websites using them." 2) "When you and your friends visit an instantly personalized site, the partner can use your public Facebook information, which includes your name, profile picture, gender, and connections. To access any non-public information, the website is required to ask for you or your friend's explicit permission." This seems contradictory unless "personal information" is taken to mean "non-public information". Or are "social plugins" and "instant personalization" not the same thing?
- TheSandyWalsh 16y agoThe way I understand it, if you have the "instant personalization" feature On (and it is by default), when you visit an enabled site, they can request your personal/non-public information to give a better experience. If you turn that feature off, they can only access your public info ... Pages and whatever else you leave open. Again, all this stuff is public by default. I'd like to hear some backup of this theory though. The big winner here is Facebook. Comments, likes and all that stuff all make they way back to the Facebook mothership. The external websites may or may not get access to that info.
- robotron 16y agoI suggest looking at the Facebook social plugins on the developer's site. Play around with them for a few minutes and you'll see that they are somewhat benign. I may be wrong and am open to someone telling me that if they present examples.