Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes, I think you can also do the same thing <code>phillee</code> answered with the Graph API instead of FQL:</p> <ol> <li>Get user's photos <code>https://graph.facebook.com/USERID/photos</code></li> <li>Get each photo's tags <code>https://graph.facebook.com/PHOTOID/tags</code></li> <li>Sort through the list of photo tags, and grab all photos with the Friend in them</li> <li>Get each photo's comments <code>https://graph.facebook.com/PHOTOID/comments</code></li> <li>Sort through the list of photo comments, and grab all comments left by the friend</li> <li>As the other answer also said: rinse and repeat for all data you want<br> <ol> <li><code>https://graph.facebook.com/USERID/feed</code></li> <li><code>https://graph.facebook.com/USERID/posts</code></li> <li>etc etc, see all connections here: <code>http://developers.facebook.com/docs/reference/api/user/</code></li> </ol></li> </ol> <p>For the interests, movies, activities, etc just make an API call for both (<code>https://graph.facebook.com/ONEUSER/music</code> and <code>https://graph.facebook.com/OTHERUSER/music</code>) and find the intersection of the two sets of data (loop through each list and save all matches to a separate list of mutual Likes)</p> <p>There are no specific API calls for friendships though, so you <em>will</em> have to build your own. My guess is that Facebook is doing exactly this on their Friendship pages :) </p> <p>It should be just as easy with FQL as with the REST API... maybe even easier with FQL since you can add WHERE conditions and get back just the data you need (<code>SELECT * FROM comments WHERE fromid = FRIENDID</code>), instead of sorting through the big list returned by the API (unless there is a way to add conditions to API request URLs?).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload