Facebook suspends personal data-sharing feature
Developers kicked back out of your undie drawer
Facebook has "temporarily disabled" a controversial feature that allowed developers to access the home address and mobile numbers of users.
The social network suspended the feature, introduced on Friday, after only three days. The decision follows feedback from users that the sharing of data process wasn't clearly explained and criticism from security firms that the feature was ripe for abuse.
Individual users had to grant permission before developers could hook into the API on Facebook's platform. However, because many users often click through permission dialogue boxes without paying attention, concerns were raised by net security firms such as Sophos that the feature might make life easier for the developers of rogue applications.
Instead of tricking users into handing over their mobile phone number before signing them up for worthless premium rate services, the personal info API feature might be abused to achieve the same end simply by fooling a potential mark into clicking through a dialogue box and installing a dodgy application - a move a greater percentage of victims are likely to fall for.
That's not what the feature was designed for, of course, but it's a plausible scenario of how it might be abused.
Greater sharing of personal information with legitimate apps also raises privacy concerns over the feature because (as initially established) users are likely to be handing over even more data to apps such as Foursquare without anything approaching informed consent.
Facebook said the benefits of the feature included the ability to "easily share your address and mobile phone with a shopping site to streamline the checkout process, or sign up for up-to-the-minute alerts on special deals directly to your mobile phone".
"As with the other information you share through our permissions process, you need to explicitly choose to share this data before any application or website can access it, and you can not share your friends’ address or mobile number with applications," a post by Facebook on its developers blog explains.
But negative feedback over the weekend has Facebook to reconsider its approach, suspending the feature for at least a "few weeks" to make it clearer that personal data was being handed over.
"We got some useful feedback that we could make people more clearly aware of when they are granting access to this data," Facebook added. "We agree, and we are making changes to help ensure you only share this information when you intend to do so.
"We’ll be working to launch these updates as soon as possible, and will be temporarily disabling this feature until those changes are ready. We look forward to re-enabling this improved feature in the next few weeks."
Facebook seems to be rediscovering the lessons Microsoft learned when its introduced User Access Control permissions to allow apps to run in Vista. Users can get irritated by constant dialogue boxes, responding by agreeing to everything they see without considering the possible consequences.
A Facebook spokesperson explained that an app can only request information it needs to operate. So if an app has no mobile phone update, it couldn't request a hook into Facebook's personal data API.
We're not convinced that this, even together with user education and a rogue application reporting system, goes far enough towards addressing security concerns that the personal information API is ripe for abuse. Although it doesn't say as much, Facebook clearly shares at least some of these concerns or it wouldn't have decided to suspend the feature. ®