Are Facebook read_stream API resolutions actually blocked for non-Facebook apps?

Question

Getting some conflicting information from Facebook at the moment about whether read_stream permission is actually out of date for advanced apps other than Facebook. I recently knew that a change was made that required access tokens for applications for read permissions.

In Facebook's graphical explorer, it looks like my existing application, which has already been granted the access token for read_stream applications, still provides access to the [user-id] / posts endpoint, although I also noticed that the search for this endpoint is in link, you go to [user-id] / feed, which also requires read_stream permission.

However, when searching for read_stream permission in reference, it now reads:

This permission is granted to applications that create a client under the Facebook brand on platforms where Facebook is not yet available. For example, Android and iOS applications will not be approved for this permission. In addition, web applications, desktop and television applications will not be granted this permission. Blockquote

I wonder if someone from Facebook or from outside can confirm that this endpoint is now closed to third-party applications, and if there is any explanation for what?

Answer 1

Now someone can use the permission " user_posts ". This new permission allows the application to access messages on a person’s timeline. This includes personal messages, messages in which they are marked, and messages that other people do on their timeline. This is a useful alternative to the news. This content was previously available with read_stream permission. User_posts permission is automatically granted to everyone who previously had read_stream permission.

Facebook platform for the platform