You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The official Facebook app, when setting a user's picture, uses the location of the user's tag in the photo (if present) to crop it. I don't know where to find the code for com.nloko.simplyfacebook.net.*, but https://graph.facebook.com/photo_fbid contains all the tags for that photo with "x" and "y" values. Doing some testing, those floating point numbers are percentages, not pixel values.
I'm not sure how you'd want to implement it. Maybe as a general option, passing optional coordinates with the picUrl, for other services that support tagging? Maybe someone will feel plucky and add facial recognition in the future.
If I could figure out how to get tags:data[foo]:x and tags:data[foo]:y where tags:data[foo]:id==uid with your JSON methods, I'd submit a patch.
The text was updated successfully, but these errors were encountered:
The official Facebook app, when setting a user's picture, uses the location of the user's tag in the photo (if present) to crop it. I don't know where to find the code for com.nloko.simplyfacebook.net.*, but https://graph.facebook.com/photo_fbid contains all the tags for that photo with "x" and "y" values. Doing some testing, those floating point numbers are percentages, not pixel values.
I'm not sure how you'd want to implement it. Maybe as a general option, passing optional coordinates with the picUrl, for other services that support tagging? Maybe someone will feel plucky and add facial recognition in the future.
If I could figure out how to get tags:data[foo]:x and tags:data[foo]:y where tags:data[foo]:id==uid with your JSON methods, I'd submit a patch.
The text was updated successfully, but these errors were encountered: