Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
facebook publish: support liking pages #349
Comments
snarfed
added
now
publish
labels
Jan 20, 2015
added a commit
to snarfed/granary
that referenced
this issue
Jan 21, 2015
|
Another real world example: http://tantek.com/2015/021/f2 :) |
snarfed
self-assigned this
Jan 22, 2015
|
thanks for looking! yup, that's it. if only it worked for users in v2.x! poor #350. i'm actually already mostly done implementing this. stay tuned! |
|
goddammit. from https://developers.facebook.com/docs/graph-api/reference/v2.2/user/likes#publish :
f'ing facebook api. i need a drink. |
added a commit
to snarfed/granary
that referenced
this issue
Jan 22, 2015
snarfed
closed this
in
snarfed/granary@bc43c3b
Jan 22, 2015
added a commit
to snarfed/granary
that referenced
this issue
Jan 22, 2015
|
Thanks for trying. Documented: http://indiewebcamp.com/POSSE_to_Facebook#API_disallows_liking_pages |
|
Reopening this one briefly. Tantek got an error message "Sorry, the Facebook API doesn't support liking pages." when trying to like a photo. |
kylewm
reopened this
Feb 2, 2015
|
sigh. should we just give up and declare facebook publish bankruptcy? :p I honestly wonder if scraping and imitating a browser would be easier or more reliable, short-lived auth cookies notwithstanding. (kidding... kinda...) |
|
I do honestly think we should give up publishing responses to Facebook... |
|
:( (that's my disbelieving, then sad, then resigned face.) ok. so. for completeness, what do we have to do first to exhaust all possibilities? post an SO question, include all of our research so far, and attach a big fat bounty? find a personal connection at facebook and ply them for information? anything else? |
|
moving discussion to #350 |
snarfed
referenced this issue
Feb 4, 2015
Closed
facebook: v2.0 api no longer allows lookup by username #350
snarfed
removed their assignment
Feb 4, 2015
|
tentatively blaming #350. holler if you disagree. |
snarfed commentedJan 20, 2015
as requested by @tantek in #41. the problem is that the page has a username, and FB requires ids in API URLs, not usernames. the fix is to look up the object by username first, then use its id.