You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
changed the title
Feature request: Bridgy backfeed reacjis on POSSEd comments
GitHub: backfeed emoji reactions on comments
Sep 1, 2022
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)
The text was updated successfully, but these errors were encountered: