{"id":860,"date":"2009-02-10T17:27:30","date_gmt":"2009-02-11T01:27:30","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/?p=860"},"modified":"2009-02-10T17:27:30","modified_gmt":"2009-02-11T01:27:30","slug":"facebook-opens-status-api","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2009\/02\/10\/facebook-opens-status-api\/","title":{"rendered":"Facebook Opens Status API"},"content":{"rendered":"

<\/span>\u201cFacebook is slowly tearing down the wall around its silo and is starting to expose more of its data to the outside\u201d (From Facebook Opens Up: Lets Developers Access Status Updates, Notes, Links, and Videos<\/a>). Now Facebook allows the third-party developers to have access to users\u2019 private data, such as status updates and notes. This is intended to make both developers more flexible in making and using applications. Moreover, Facebook wants to make more and more people use Facebook by join the OpenID foundation. However, weaknesses and potential security problems are found by doing this update for Facebook\u2019s API.<\/p>\n

\n

Assets and security goals<\/p>\n