Live data from Hacker News

Facebook’s Instant Personalization Is the Real Privacy Problem

gigaom.com

31–40 of 41 posts

Re: Facebook’s Instant Personalization Is the Real Privacy Problem

#32
post #24

What's the best way to block this entirely? /etc/hosts won't work because it's not on a subdomain (the iFrame loads from http://www.facebook.com/plugins/activity.php ). This would make a nice Chrome/Firefox extension.

I added http://www.facebook.com/plugins/ and https://www.facebook.com/plugins to AdBlocker's filters in Safari.

It seems to have removed all Open Graph stuff from the web for me.

Re: Facebook’s Instant Personalization Is the Real Privacy Problem

#33
The idea is that Pandora is a somewhat hard concept to explain to new users — before it existed, people didn’t have their own personalized radio stations based on similarities between artists and song.

Last.fm always generated you radio stations based on your scrobbles or by tags you type and predates Pandora

Re: Facebook’s Instant Personalization Is the Real Privacy Problem

#34
post #24

What's the best way to block this entirely? /etc/hosts won't work because it's not on a subdomain (the iFrame loads from http://www.facebook.com/plugins/activity.php ). This would make a nice Chrome/Firefox extension.

> What's the best way to block this entirely?

A greasemonkey script to always click 'No Thanks'.

Re: Facebook’s Instant Personalization Is the Real Privacy Problem

#36

Earlier quoted context omitted.

That is some really scary stuff in the link you gave!!! People need to realize that it's not worth the $0.25 off a can of green beans you get by using a loyalty card, if a sleazy merchant is going to swoop in at some vulnerable time in your life and help separate you from hundreds or thousands of your dollars.

Can you give an example of how they are going to 'help separate you from hundreds or thousands of your dollars'?

Did you read the document? They use psychological tactics combined with an outrageous amount of your personal data in order to market to you. Let's supposed you just had a child or spouse die, more specifically, you were just widowed. They will be able to garner that fact from your spending habits or public records (or perhaps FB data) and combine it with all the other info they have on you, and then might try to sell you some shady investment or insurance. Their job is to get you to buy something you don't need. They're working on it while you sleep. Many people are not adequately equipped to resist their tactics.

Re: Facebook’s Instant Personalization Is the Real Privacy Problem

#37

To disable, Go To: Account > Privacy Settings > Applications and Websites > and [UNCHECK] "Instant Personalization"

Unchecking that box only stops the personalization from happening automatically. The floating toolbar still appears asking if you'd like to opt-in (at least on yelp.com)

Re: Facebook’s Instant Personalization Is the Real Privacy Problem

#38
post #30

Years ago, when caller ID was becoming commonplace, a company (I think it was American Express) started answering customer calls by name--- "Hello Mr. Jones, how can we help you." This proved to be very unpopular with customers and they stopped doing it... they probably still use the caller ID but don't let you know that they are.

It probably also annoyed Mrs. Jones when she made calls using the Jones' shared line which was in Mr. Jones' name.

Re: Facebook’s Instant Personalization Is the Real Privacy Problem

#39
post #27
post #24

What's the best way to block this entirely? /etc/hosts won't work because it's not on a subdomain (the iFrame loads from http://www.facebook.com/plugins/activity.php ). This would make a nice Chrome/Firefox extension.

Any decent browser should be able to block content by URL. Use your adblocker.

My adblocker (in Chrome) loads resources before removing them from the DOM. I simply want to block this before the request is made.

Re: Facebook’s Instant Personalization Is the Real Privacy Problem

#40
post #24

What's the best way to block this entirely? /etc/hosts won't work because it's not on a subdomain (the iFrame loads from http://www.facebook.com/plugins/activity.php ). This would make a nice Chrome/Firefox extension.

If you're talking about blocking on the enterprise network, check out this resource. It's a whitepaper called “To Block or Not. Is that the question?”

http://bit.ly/9f8WOT

It has lots of insightful and useful information about identifying and controlling Enterprise 2.0 apps (Facebook, Twitter, Skype, SharePoint, etc.)

Post reply on HN