Skip to content
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

GitHub: backfeed emoji reactions on comments #1076

Open
tantek opened this issue Oct 18, 2021 · 1 comment
Open

GitHub: backfeed emoji reactions on comments #1076

tantek opened this issue Oct 18, 2021 · 1 comment
Labels

Comments

@tantek
Copy link
Contributor

tantek commented Oct 18, 2021

In Bridgy backfeed documentation it says "Bridgy detects and sends webmentions for … GitHub comments and emoji reactions on your issues and pull requests" which would seem to imply that Bridgy does not yet send webmentions for emoji reactions (reacjis) on POSSEd comments on GitHub issues and pull requests, e.g. the reacjis on this comment POSSEd by Bridgy.

According to GitHub API docs: List reactions for an issue comment it looks like this information is available in the GitHub API. It would be great if Bridgy could add support for backfeeding reacjis on POSSEd comments! Thanks for your consideration.

(Originally published at: https://tantek.com/2021/291/b1/bridgy-backfeed-reacji-on-comments)

@snarfed
Copy link
Owner

snarfed commented Oct 21, 2021

Looked into this a bit. It will take some work under the hood to make Bridgy backfeed to comments as well as original posts, which it doesn't currently do. Doable! But substantially more work than just fetching reactions on comments.

(Twitter seems like an exception, but due to Twitter's data model that everything is a tweet, replies are also handled as original posts.)

@snarfed snarfed changed the title Feature request: Bridgy backfeed reacjis on POSSEd comments GitHub: backfeed emoji reactions on comments Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants