Why do I need the FB "user_status" permission if I have already been granted "user_posts"?
In Facebook API v2.3, "user_posts" sounds like a superset of "user_status". This is true? Why would I ever need "user_status" if I already have "user_posts"?
user_status
Provides access to a person's status. These are Facebook posts and do not include links, videos, or photos.
user_posts
Provides access to messages on a person. Includes own posts, posts they are tagged with, and posts made by other people in their timeline.
https://developers.facebook.com/docs/facebook-login/permissions/v2.3#reference-user_status https://developers.facebook.com/docs/facebook-login/permissions/v2.3#reference-user_posts
source to share
Here is an example of when you need or need to integrate user_status permission over user_posts permission ...
Suppose you want to run a sentiment analysis on your facebook user ... if you crawl / parse user_posts then you won't get unique sentiments for that user, you get the feeling of a whole conversation as user_posts includes posts from this fb user friends. If facebook only offers user_posts, and you only wanted moods for that user, then you would have to spend a lot of time and money developing a cleanup script to filter out all the noise, including posts from fb's friends. But luckily facebook has made developers intuitively easier in this situation by opening the user_status permission ... with this permission I can run sentiment analysis only on text that is unique to that user only, withoutit is necessary to write a script that filters out all the noise. Because of this, I feel the mood of the user, not the feeling of a conversation. So it all depends on your use case.
Hope this helps!
source to share