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
{{ message }}
This repository has been archived by the owner on Jan 31, 2024. It is now read-only.
When reacting from different instances, custom emoji reactions that are the same have separate counts depending on which instance they were sent from.
Proposed implementation idea
It would be awesome to have these grouped by image hash. Also, when a custom emoji reaction from a remote instance that is also present on the local instance is clicked, nothing happens. I propose checking for the image hash on the local instance, and if one with the same hash is present, send that.
The text was updated successfully, but these errors were encountered:
This was discussed in the discord already and was advised against by mulitple people.
"I actually think this would be pretty easy to implement, and should work on any instance. I'd need to see a formal JSON-LD context to be sure. But just because you can do it doesn't mean that you should!"
"It's just a limitation of activitypub as far as I can tell, I'm sure you could commit some crimes to make that work but it would only work on instances running the same software as yours, like a flag that merges emojis of the same name together when they're shown as a react
(this is a terrible idea and I wouldn't ever recommend implementing something like that)
"
Summary
When reacting from different instances, custom emoji reactions that are the same have separate counts depending on which instance they were sent from.
Proposed implementation idea
It would be awesome to have these grouped by image hash. Also, when a custom emoji reaction from a remote instance that is also present on the local instance is clicked, nothing happens. I propose checking for the image hash on the local instance, and if one with the same hash is present, send that.
The text was updated successfully, but these errors were encountered: