facebook opengraph - Trying to understand the restriction difference between the Open Graph "follow" and "like" actions -

Looking at these 2 articles: like:

You can publish stories The people who write Facebook posts from your own wall in the same way as your Open Graph pages, the stories appear in the news feeds of those people who have clicked on the Like button on the Open graph page.

You can also publish it using our API. If you use your OpenGraph page with fb: app_id meta tag with the Facebook app, you can publish updates to those users who have liked your pages via the graph API.

Follow:

Similar to the ability to subscribe to user's posts on Facebook, users can now open graphs of other users with a specific app You can follow the activities. . For example, on the movie review site, users can follow their favorite movie reviewers. When a user follows another user in your app, then all content published by your publisher in the app is eligible to appear in the news feed, even if they are not a Facebook friend (until the privacy of published works Permission is not granted to see the follower post):

It appears that in both cases you can create an open graph object You can create that object by using an example given in the "Follow" or "Like" example, which are outside Facebook and

http / / www. Rottentomatoes.com / celebrity / tom_hanks /

If you decide on "Hate" Tom Hanks on the site, pages can publish news about Tom Hanks and they will be in your news feed. Will appear. (All the permissions are okay, no worries).
If you decide to "follow" Tom Hanks on the site, then if I understand the requirements posted by Facebook correctly:

In this case, the URL The document returned by fetching should contain an FB: Profile_ID meta tag that indicates the user's Facebook ID:

     
 
 We recommend that the content of this field be third-party_id of a user, which is retrieved by adding URLs = fields = third_party_id of requests when retrieving user information. , And the graph API is described in the documentation for the user object.  
 This tag is not required, and the operation behind it will be successful, though the followers will see the activity in their news feeds.   
   
 
 Because the page stays outside of Facebook, it will not have one-third side and therefore if the site publishes news about Tom Hanks , You will not see news that will appear in your news feed.  
 Is there any reason why things behave like this?   
 
 
 Similar to the same, publish the same story though, the app has two Facebook Allow users to create a "subscribe" relationship between users. Consider the example below, which also shows how  third_party_id  is used to create such a relationship:  
 You say William has your app Followed the Claude in and that your app has successfully updated Facebook. Whether you provide the  third_party_id  of the claudet, William's publication on William's news feed will be published on William's News Feeds.  
 Although CloudAut is provided with  third_party_id , then William will start getting all the claudet actions published by your app. Now, this is great but definitely to do this, Facebook should know "Who is the Claudette", which it does  third_party_id .  
  third_party_id  The follow-up action is shared on William's news feed and possibly with William's friends. But this is once a matter of expanding the varity by providing  third_party_id  and Claudette makes the client on their app to ensure continuous flow for Williams.