Friday, March 4, 2011

F*&%@ Book is EVERY thing Against Our Needs, Security, and Personal Privacy

Again, another reason why throwing billions at a boy, Zuckerberg of F*&%@ Book, is absolutely counter to our constitutional rights to privacy. His sleazy lack of ethics and profiteering will put all F*&%@ Book users in the trunk of the security creeps and marketing criminals driving our culture closer to the brink if infantilism and irrelevance.

Is this too strong language about F*&%@ Book? Absolutely not.

Read what came out March 4, 2011

Breakout quote -- from Alternet today, March 4, 2011:

[As AlterNet writer Allan Badiner wrote this summer in an article called "How Facebook Betrayed Users and Undermined Online Privacy":

... users are creating a cumulative data repository of all the relationships in the entire world and the intimate details of everyone’s lives. The databases and algorithms employed at Facebook to store, crunch, and make inferences about you are far greater holders of data than any government agency.

Several times in the past, users have found their information divulged and have had to go back and re-set settings to have the same level of privacy as before. In 2007, MoveOn.org targeted Facebook in a petition, urging members to express concern with vanishing privacy on the site.]

Facebook Will Share Users' Phone Number, Email and Address with Third Parties

In a move that was announced, and then quietly postponed, back in January, Facebook is again planning to allow third-party applications (folks who write games and applications that use the Facebook interface) to access users' most personal contact information--including addresses, phone numbers, and email addresses. The social networking mega-site would ask users' explicit permission to do this, as it currently does when users want to tap into these often frivolous third-party apps--and the company is also "considering" an age cap that would prevent teenagers and children from allowing this information to be released.

From the original post at Facebook's in-house Developer blog in January:

We are now making a user’s address and mobile phone number accessible as part of the UserGraph object. Because this is sensitive information, we have created the new user_address and user_mobile_phone permissions. These permissions must be explicitly granted to your application by the user via our standard permissions dialogs.
But this announcement quickly drew ire from privacy advocates who were concerned that these third-parties might use the information for any number of reasons. And then the company suspended the application within a few days with plans to re-open it--which it is now doing. If you want to be preemptive and block the site from releasing this information, here is a how-to guide from Zdnet.com.


Those expressing concern with the new move included U.S. Reps. Edward Markey (D-Mass) and Joe Barton (R-Texas) of the house "privacy caucus" forcefully spoke up asking the company to reconsider. Markey received a long response from the company's Vice President of Global Public Policy, Marni Lavine, which he posted on his website here.

Levine assured the Congressmen that the company was working to make its permission-granting process clear, but just a few days ago the congressmen said they weren't fully reassured, and reiterated their demands:

“Mobile phone numbers and personal addresses, particularly those that can identify teenagers using Facebook, require special protection,” said Rep. Markey in a statement. “We must ensure that this sensitive information is safeguarded, with clear, distinct permissions so that users know precisely what’s in store when they opt to share this data with third parties. Moreover, simple, easily accessible tools are needed so users can rescind these permissions if they subsequently find they no longer want their information in the hands of third parties."

No comments:

Post a Comment

This blog is brought to you by

This blog is brought to you by
Paul Haeder

Fuse Washington

Fuse Washington