Skip to content

facebook publish: POSSE like should return FB POSSE like permalink #334

Closed
tantek opened this Issue Jan 4, 2015 · 6 comments

2 participants

@tantek
tantek commented Jan 4, 2015

When you use Bridgy to POSSE a like post to Facebook, Bridgy should return to you the new permalink of the FB POSSE like.

Background: http://indiewebcamp.com/irc/2015-01-03#t1420318033946

I asked: "I don't think Bridgy Publish returns the FB permalink of the POSSE like of a FB object, does it?"
and @kylewm thinks "it should if it doesn't"

And: http://indiewebcamp.com/irc/2015-01-03#t1420332232527

@snarfed
Owner
snarfed commented Jan 4, 2015

thanks for filing! I'd definitely like to do this.

first, we have to figure out how to get or generate that like permalink. FB doesn't return it in the API call that creates the like. I'll keep looking, but let me know if you have any ideas!

@tantek
tantek commented Jan 4, 2015

Perhaps immediately make a call to check the user's "/allactivity" and grab the permalink from the most recent like post there? Possible race condition with other FB clients between the two calls, but unlikely. Can also double check the timestamp.

@tantek
tantek commented Jan 4, 2015

In case it helps - all the "NovemberProject's photo" like posts here http://tantek.com/2015/002/f now have a manually added syndication link to the FB POSSE copy of the like, for all them that didn't 404 (#331) error out when trying to Bridgy Publish the POSSE like to FB.

@tantek tantek changed the title from Bridgy Publish of POSSE like to Facebook should return FB POSSE like permalink to facebook publish: POSSE like should return FB POSSE like permalink Jan 4, 2015
@snarfed
Owner
snarfed commented Jan 4, 2015

ongoing research:

@snarfed
Owner
snarfed commented Jan 4, 2015

...tentative conclusion so far is that we don't know how to get the like permalinks. :/ deprioritizing for now, sadly.

@snarfed
Owner
snarfed commented Mar 12, 2015

...and closing altogether now that publish for facebook likes and comments is dead (#350). :(

@snarfed snarfed closed this Mar 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.