Facebook has just revealed some details on an issue that occurred with some developer applications accidentally going offline. In the social networking company’s first post-mortem, it hoped to shed some light on what steps it was taking to prevent the occurrence.
The incident happened on August 13 and Facebook said that during routine monitoring to remove malicious apps from being used, its sweep instead inadvertantly targeted high-quality apps. Once this mistake was detected, Facebook stopped what it was doing and set about to repair the damage it caused.
Word first came out through a thread on Hacker News when a developer from Chute wondered why his startup’s applications were randomly disabled. A Facebook employee responded in the comments apologizing for the mistake, saying “We’re working on restoring the set of apps that were accidentally disabled. Many of them are back, some are still in process.”
Facebook’s developer advocate David Weekly chimed in as well, explaining:
We have systems that block spammy apps that are 99.9% of the time really incredibly sophisticated and get a ~0% false positive rate.
This is a case of the 0.1%. :( Folks here are scrambling to undo this. Very, very sorry. Things should now (17:47 PT) be all set.
But why did it take so long to restore? According to Facebook: “The process took longer than expected because of the number of apps affected and bus related to the restoration of app metadata.”
In order to prevent this from happening in the future, Facebook is implementing two new steps:
- We will create better tools to detect overly broad patterns and put in place better processes to verify that all apps matched are indeed malicious.
- We will address the bugs and bottlenecks that made the recovery process slower than expected.
More to follow. Please refresh for updates.
via http://feedproxy.google.com/~r/TheNextWeb/~3/risvUynmVTU/
No comments:
Post a Comment