Getting some conflicting information from Facebook currently on whether or not the read_stream permission is actually deprecated for non-Facebook branded apps moving forward. I know recently the change was made to require app-specific access tokens for read-stream permissions.
In the Facebook graph explorer it looks as though my existing application which was already granted an app-specific access token for the read_stream persmission is still providing access to the [user-id]/posts endpoint, although I also noticed that searching for this endpoint in the reference takes you now to [user-id]/feed, which also requires the read_stream permission.
When searching the read_stream permission in the reference however, it now reads:
This permission is granted to apps building a Facebook-branded client on platforms where Facebook is not already available. For example, Android and iOS apps will not be approved for this permission. In addition, Web, Desktop and TV apps will not be granted this permission. Blockquote
Wondering if anyone from Facebook or outside can actually confirm that this endpoint is now closed to 3rd-party apps, and if there is any explanation whatsoever for why?
Now someone can use "user_posts" permission - This new permission allows an app to access the posts on a person's Timeline. This includes the someone's own posts, posts they are tagged in and posts other people make on their Timeline. This is a useful alternative to News Feeds. Previously, this content was accessible with the read_stream permission. The user_posts permission is automatically granted to anyone who previously had read_stream permission.
来源：https://stackoverflow.com/questions/26540854/facebook-graph-api-read-stream-permission-actually-blocked-for-non-facebook-bran