@trwnh @helene hi, i wrote this PR indeed!

i kind of gave up on it as it's rather low-priority, i had issues figuring out how do things efficiently, and as i understand, @noellabo was working on a similar feature on their fork, so i was hoping we could use that implementation instead

tbh, i haven't kept track of the state of @noellabo's implementation, and i have other priorities right now (groups, reply policies, and a few other things)

to answer your question, my main issue is that you wouldn't be aware of existing reactions when discovering a new post, though i'm not sure how much of an issue that is in practice; exposing a collection of reactions would probably help a lot, but reaction forwarding may be needed to, idk

@Claire @trwnh @noellabo Alright, that makes sense! I’ll be keeping a close eye on those other things, too

Fedibird’s implementation seems to be supporting Misskey custom emoji reactions (as well as Akkoma’s, now), while also allowing creating them and sending them out. They seem to be using the litepub:EmojiReact activity type. I believe it only supports one reaction per user, per post, in its current state, much like Misskey (but unlike Pleroma/Akkoma, which allow many). They currently expose a Collection of reactions, though I do not know if anything makes use of it. It seems overall more feature-complete, and I’m seeing Fedibird users use them fairly frequently (and they seem to have no issues viewing reactions from Misskey/Pleroma/Akkoma themselves!)

Misskey, Pleroma/Akkoma and others do not expose reactions via an ActivityStreams Collection, and they do not expose replies via a Collection either. Neither of those forwards replies, either, which is very different from what Mastodon does. Mastodon forwarding reactions like it forwards replies would seem indeed consistent to that behaviour! I could look into exposing reactions via a Collection for Pleroma and forks, if Mastodon would be interested. (This would be quite an endeavour, as we have no support for Collections currently as far as I know, but that should be feasible!)

@helene @trwnh @Claire Here is an example of an actual Fedibird post.
https://fedibird.com/@noellabo/108371701774094182

See here for the json representation.
https://fedibird.com/@noellabo/108371701774094182.json

Own collections.

{
@context: [
{
fedibird: "http://fedibird.com/ns#",
emojiReactions: {
@id: "fedibird:emojiReactions",
@type: "@id"
}
}
]
},
emojiReactions: "https://fedibird.com/users/noellabo/statuses/108371701774094182/emoji_reactions",

If each implementation supports this collection, emoji reactions can be federated. [参照]

@noellabo @helene @trwnh i'm not sure i like using Like for custom reactions as the custom reaction could convey something very different from a Like…

i'm also not very fond of the emoji reactions spanning multiple lines, but i'm not sure what we can do about that

in any case, i would welcome a Mastodon PR for that! but i'm not sure when i'd be able to review it, and Gargron hasn't been very active either with reviewing PRs

@noellabo @helene @trwnh also i don't know if fedibird, pleroma, or misskey supports that, but it think it would be important to be able to easily block and remove reactions (especially custom ones) as i could imagine that being a harassment vector

@Claire @helene @trwnh Fedibird's specification excludes from view emoji reactions of users who are muted and blocked by the viewer.

It is not possible to remove specific emoji reactions. federation is difficult.

I'd like to refer to the implementation there because it has the same problem as the mechanism to reject replies.

@noellabo @helene @trwnh right, but i can see figuring out who reacted with offensive/triggering stuff and blocking them may be far more cumbersome than with a reply

as for rejecting replies, i'm currently drafting a FEP to hopefully address that (though of course it requires third-parties to actually verify it)