Note that there are some explanatory texts on larger screens.

plurals
  1. USgiff
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COJust so its clear - no, this is not SSO compatible - users will have to give you credentials at least once for your app. No way around it. But I'd rather do this and get all my auth done in one chunk rather than create the expectation that SSO is available.
      singulars
    2. COYes, you'll get a valid auth token for making graph request. You have to sign in somewhere, so yes, this will put up a login challenge when you call it, if the cookies are not valid anymore. You can keep the auth token and cookie stored, and re use them - if you request offline access in your permissions, the cookies are good for a long while. No, this will NOT be compatible with things that depend on SSO, like what FB calls deep linking. You have to choose your poison. There is no way to use the FB apps SSO as your aunt method and open a web view in your app without re-authenticating.
      singulars
    3. COAppreciate the idea, but that would mean dropping status updates, links or photo posts from applications like Twitter, the Facebook app in iPhone, external websites that enable link sharing. Those are actual posts that are valid. These are marked as one thing (a status update or a link), but actually are something else, an "activity" update as it were. Really, their "type" field should identify what they are.
      singulars
 

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