publish: FB like POSTs sometimes 404 #331

Closed
snarfed opened this Issue Jan 2, 2015 · 7 comments

Comments

Projects
None yet
2 participants
@snarfed
Owner

snarfed commented Jan 2, 2015

example log.

we're POSTing to e.g. https://graph.facebook.com/NovemberProjectSF_568825249920639/likes, but maybe it should be either https://graph.facebook.com/568825249920639/likes or https://graph.facebook.com/NovemberProjectSF/568825249920639/likes? not sure which yet, or if either will work.

...but sometimes that URL format works. maybe the difference is user id vs username? post object id vs photo? here's an example that worked by POSTing to https://graph.facebook.com/753470156_10155052328930157/likes

thanks to @tantek for the report!

@snarfed snarfed changed the title from publish: FB likes sometimes use the wrong API URL to publish: FB like POSTs sometimes 404 Jan 2, 2015

@tantek

This comment has been minimized.

Show comment
Hide comment
@tantek

tantek Jan 2, 2015

Contributor

This is very odd as all I did was copy the URL of the hyperlinked date/time from several phosts/photos on FB - confusing that somehow they are treated differently by FB.

Contributor

tantek commented Jan 2, 2015

This is very odd as all I did was copy the URL of the hyperlinked date/time from several phosts/photos on FB - confusing that somehow they are treated differently by FB.

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Jan 2, 2015

Owner

ah, no, sorry if i was unclear. bridgy breaks down the u-like-of URL you give it, then reconstructs variants when it needs them. the maybe bad URL is a graph.facebook.com API URL.

Owner

snarfed commented Jan 2, 2015

ah, no, sorry if i was unclear. bridgy breaks down the u-like-of URL you give it, then reconstructs variants when it needs them. the maybe bad URL is a graph.facebook.com API URL.

@tantek

This comment has been minimized.

Show comment
Hide comment
@tantek

tantek Jan 2, 2015

Contributor

Just manually iterated through all the likes on http://tantek.com/2015/002/f and of the 10 there, only http://tantek.com/2015/002/f2 and http://tantek.com/2015/002/f3 caused the 404 bug (and consistently so). All the other http://tantek.com/2015/002/f posts (f1-f10) seemed to work fine.

Contributor

tantek commented Jan 2, 2015

Just manually iterated through all the likes on http://tantek.com/2015/002/f and of the 10 there, only http://tantek.com/2015/002/f2 and http://tantek.com/2015/002/f3 caused the 404 bug (and consistently so). All the other http://tantek.com/2015/002/f posts (f1-f10) seemed to work fine.

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Jan 2, 2015

Owner

thanks for the info!

Owner

snarfed commented Jan 2, 2015

thanks for the info!

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Jan 21, 2015

Owner

looks like this is because the FB API doesn't like usernames anywhere except in bare object lookups. specifically, ids like NovemberProjectSF_568825249920639 definitely don't work. it should be the NovemberProjectSF page id instead.

sounds like this is actually the same problem as #349.

Owner

snarfed commented Jan 21, 2015

looks like this is because the FB API doesn't like usernames anywhere except in bare object lookups. specifically, ids like NovemberProjectSF_568825249920639 definitely don't work. it should be the NovemberProjectSF page id instead.

sounds like this is actually the same problem as #349.

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Jan 21, 2015

Owner

confirmed, at least for reading, but should apply to writing too. /276430682493432_568825249920639/likes works, /NovemberProjectSF_568825249920639/likes doesn't.

Owner

snarfed commented Jan 21, 2015

confirmed, at least for reading, but should apply to writing too. /276430682493432_568825249920639/likes works, /NovemberProjectSF_568825249920639/likes doesn't.

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Jan 22, 2015

Owner

this is mostly fixed by the changes in #349 and nearby. the part that's not fixed is #350, which is a whole other can of worms. :/

Owner

snarfed commented Jan 22, 2015

this is mostly fixed by the changes in #349 and nearby. the part that's not fixed is #350, which is a whole other can of worms. :/

@snarfed snarfed closed this Jan 22, 2015

snarfed added a commit to snarfed/granary that referenced this issue Jan 22, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment