New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facebooks new "Reactions" not being pulled? #626

Closed
armingrewe opened this Issue Feb 24, 2016 · 9 comments

Comments

Projects
None yet
4 participants
@armingrewe

armingrewe commented Feb 24, 2016

Facebook implemented their new "Reactions" feature today, which has replaced the old "Like" button. I'm not 100% sure, but I think bridgy doesn't seem to pull those now? I'm fairly sure I've had a few "reactions" including a "Love" which haven't pulled through.

Any ideas?

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Feb 24, 2016

Owner

interesting! doesn't look like they're in the API yet. i'll keep an eye on the changelog.

fwiw, i don't actually see them in my FB account yet. :P

Owner

snarfed commented Feb 24, 2016

interesting! doesn't look like they're in the API yet. i'll keep an eye on the changelog.

fwiw, i don't actually see them in my FB account yet. :P

@snarfed snarfed added the listen label Feb 24, 2016

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Feb 24, 2016

Owner

oh, btw, i'm not sure exactly how we'd backfeed these. i guess reacji? but we'd special case the thumbs up one and keep interpreting that as a like? or maybe they'd all be likes, and we'd include the emoji as content? except doesn't seem appropriate for the negative ones, e.g. 😢 and 😠. who knows.

Owner

snarfed commented Feb 24, 2016

oh, btw, i'm not sure exactly how we'd backfeed these. i guess reacji? but we'd special case the thumbs up one and keep interpreting that as a like? or maybe they'd all be likes, and we'd include the emoji as content? except doesn't seem appropriate for the negative ones, e.g. 😢 and 😠. who knows.

@aaronpk

This comment has been minimized.

Show comment
Hide comment
@aaronpk

aaronpk Feb 24, 2016

Contributor

There has been some experiments with posting and receiving reacji documented here: https://indiewebcamp.com/reacji#How_to_markup

Should be simple enough to send an in-reply-to URL with the content being the reaction. It has the added benefit of receivers treating them as regular comments if they don't roll them up like Ben does here: https://ben.thatmustbe.me/note/2015/12/8/2/

Contributor

aaronpk commented Feb 24, 2016

There has been some experiments with posting and receiving reacji documented here: https://indiewebcamp.com/reacji#How_to_markup

Should be simple enough to send an in-reply-to URL with the content being the reaction. It has the added benefit of receivers treating them as regular comments if they don't roll them up like Ben does here: https://ben.thatmustbe.me/note/2015/12/8/2/

@armingrewe

This comment has been minimized.

Show comment
Hide comment
@armingrewe

armingrewe Feb 24, 2016

Yes, I was wondering that as well. There are 6 options now, including the original "like". The new ones are Love, Angry, Sad, Haha and Wow. Just saying "xyz reacted to this" seems wrong as well.

I can see them since I got home about three hours ago (it's 21:00hrs here now), but I hear not everyone can see them yet.

armingrewe commented Feb 24, 2016

Yes, I was wondering that as well. There are 6 options now, including the original "like". The new ones are Love, Angry, Sad, Haha and Wow. Just saying "xyz reacted to this" seems wrong as well.

I can see them since I got home about three hours ago (it's 21:00hrs here now), but I hear not everyone can see them yet.

@armingrewe

This comment has been minimized.

Show comment
Hide comment
@armingrewe

armingrewe Feb 25, 2016

Quick update after this morning's post: it looks like if from the six options the "like" is used it still comes through on bridgy. If they pick one of the five new options they are not coming through. I'll keep watching and update of I spot anything different.

armingrewe commented Feb 25, 2016

Quick update after this morning's post: it looks like if from the six options the "like" is used it still comes through on bridgy. If they pick one of the five new options they are not coming through. I'll keep watching and update of I spot anything different.

@barnabywalters

This comment has been minimized.

Show comment
Hide comment
@barnabywalters

barnabywalters Mar 29, 2016

+1 it’d be great to get the other reactions implemented as reacji, if they ever show up in the API

barnabywalters commented Mar 29, 2016

+1 it’d be great to get the other reactions implemented as reacji, if they ever show up in the API

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Apr 12, 2016

Owner

woo! they did indeed add a reactions API in v2.6, announced today at F8.

https://developers.facebook.com/blog/post/2016/04/12/introducing-graph-api-v26/
https://developers.facebook.com/docs/graph-api/reference/post/reactions

the downside is that we have to upgrade all of our facebook usage to API v2.6...i assume? i wonder if we could just use v2.6 for reactions. i think we can't because access tokens are API version specific, but not sure. worth investigating.

if we do need to upgrade, that will require #496 and #433 at least, probably more.

Owner

snarfed commented Apr 12, 2016

woo! they did indeed add a reactions API in v2.6, announced today at F8.

https://developers.facebook.com/blog/post/2016/04/12/introducing-graph-api-v26/
https://developers.facebook.com/docs/graph-api/reference/post/reactions

the downside is that we have to upgrade all of our facebook usage to API v2.6...i assume? i wonder if we could just use v2.6 for reactions. i think we can't because access tokens are API version specific, but not sure. worth investigating.

if we do need to upgrade, that will require #496 and #433 at least, probably more.

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Apr 12, 2016

Owner

ooh this looks like it will help find everything we need to upgrade: https://developers.facebook.com/tools/api_versioning

Owner

snarfed commented Apr 12, 2016

ooh this looks like it will help find everything we need to upgrade: https://developers.facebook.com/tools/api_versioning

@snarfed

This comment has been minimized.

Show comment
Hide comment
@snarfed

snarfed Apr 13, 2016

Owner

huh. i was actually able to make a v2.6 API request, /212038_10102223481816413?fields=reactions, with a v2.2 access token after all. so i guess access tokens aren't versioned after all, or at least aren't strictly versioned, so we can mix and match different API version requests with the same token. lets us upgrade versions gradually, which is nice.

https://developers.facebook.com/docs/apps/versions#calling_older_versions

Owner

snarfed commented Apr 13, 2016

huh. i was actually able to make a v2.6 API request, /212038_10102223481816413?fields=reactions, with a v2.2 access token after all. so i guess access tokens aren't versioned after all, or at least aren't strictly versioned, so we can mix and match different API version requests with the same token. lets us upgrade versions gradually, which is nice.

https://developers.facebook.com/docs/apps/versions#calling_older_versions

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