Topic-icon Importing all FB status without privacy considerations

Active Subscriptions:

None
Hi,

We are using JFBconnect for Jomsocial registration and login. It is a good feature to import user's status message from Facebook to Jomsocial.
However if an user has shared something using a custom privacy setting in Facebook, then it's better not to import that status message. It is meant for only a selected group. We shared a status message using a custom privacy setting (not public) and this message was imported in Jomsocial.

This can lead to privacy issues and annoy users. How can we only import status updates that are public?
The topic has been locked.
Support Specialist
13 years 10 months ago #25364 by alzander
We're looking into this. At one point, I believe, Facebook would only return the public posts by default. A special setting was required to ask for private posts too, which we didn't do. So, we should only pull in public posts. It's always possible that's changed and we missed it though.

We definitely agree that only public posts should be fetched. We'll let you know what we find, but it may be a few days before we get an answer to you.

Thanks for the tip,
Alex
The topic has been locked.
Active Subscriptions:

None
13 years 10 months ago #25526 by sougatab
Any updates on this issue?
The topic has been locked.
Support Specialist
13 years 10 months ago #25543 by alzander
Sougatab,
Sorry to say, but not yet. This, and a few other JomSocial investigation issues, are high on our investigation list for early next week. We should hopefully have some more information and either a code modification or new version available to address this next week. That's the goal assuming we can find a good solution. From initial investigation, it looks very reasonable to not pull in private posts, but I just can't guarantee it yet.

Thanks for your patience,
Alex
The topic has been locked.
Support Specialist
Wanted to circle back to this post. We've been doing a bit of investigation, and getting the privacy information is possible, but in a very weird way. Basically, the "statuses" field from Facebook does not show the privacy value of any of the user's status. Quite annoying.

However, if we grab the user's "feed", we can see their status posts as well as the privacy of each of those statuses. However, there can be hundreds of posts in a user's feed, so we'd need to sift through all of them to find the last feed item that was a) a status and b) set to be public. We are looking into doing this, but it's a bit more effort than we were expecting. Additionally, we need to take loading time into account as this could slow down the registration process a bit depending on how far back we have to go to fetch the right 'last' status. Alternatively, we could just take the first 25 feed items (what is returned by default) and only use one from there, if we find it. If not, the user's status would not be imported.

It's a weighing game of a few different problems, and we're trying to work out the best. Until now, this issue hasn't been brought up. Additionally, JomSocial's built-in Facebook functionality imports statuses the same way (regardless of the FB privacy setting). So this seems to be the commonly accepted approach, for better or worse.

Again, we're still looking into the best solution. If you have feedback on the ideas above, I'd love to hear them. This won't be as quick a fix as I originally hoped though.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
Nice to hear from you regarding this issue.
We believe that both privacy and speed are important. You can limit searching to 10 posts and in case there are no public posts, then the status field will remain blank.
During our user testing, some users were worried that we were violating their privacy by pulling all status messages. They said it was better to have a blank status, then to display a private status. There is no need to search for all feeds and slow down the registration process. You can try to provide an option in the backend for the site administrator to decide how many feeds should be searched.
The topic has been locked.