It isn't...today. Remember, this app was deployed many years ago, prior to the 2014 API neutering.

I didn't think it was. The API docs have always said that the thread endpoint is only available to the developers of the app making the request. It's possible to get the contents of the inbox though.

https://developers.facebook.com/docs/graph-api/reference/v2....

You used to be able to build an alternative client using Facebook's published API.

I trained my predictive keyboard on Android on my Facebook messages and emails.

I could imagine interesting apps designed to riff on your launguage patterns

There are a lot of valid uses. Why would it be better for your data to be locked up and unexportable?

False equivalence. Exportable doesn't mean acessible to the world.

The commenter didn’t make that “false equivalence.” Their point is that there are valid reasons a user might want to allow an application to access their messages.

For example, reddit’s API allows applications to access messages, which is useful for third party clients.

But someone could pay you for your exported Facebook data (which can include data from friends such as your message history, etc). From my understanding, this is essentially what CA did. CA just obfuscated they were doing this by using the Facebook developer program to automate this process and Mechanical Turk to pay users to give them their data. I agree the Facebook developer program made it really easy to phish for this data.