執筆依頼があり、集英社オンラインでMastodonについての記事を書きました。
https://shueisha.online/culture/18417
20〜30代がメインターゲットの、スマートフォンで情報収集している層を想定した媒体だそうです。
皆さんには物足りない内容で至らぬところもあるかと思いますが、お手柔らかにw
ざっくり、
・MastodonはTwitterの代替を目指して作られた
・Twitterの問題を踏まえて、分散の仕組みにした
・Twitterから移行しなきゃと思って選ぶのが別の商用SNSじゃしょうがないから、Fediverseにしとけ
・とはいえTwitterと同じものはここにはないからそれは承知しとけ。あとみんなで来ないと無理
といったことを書きました。
時事は枕なので適当ですが、まだイーロン・マスクさんに振り回されている状況には変わりがないですね……。
been looking at https://github.com/mastodon/mastodon/pull/13275 and i'd like to know who to contact for this, as this sounds like the author of this PR wants to have a collection of the reactions exposed via the object or something?
i'd like to know what they'd want to see in Pleroma for it, exactly, though I do not think changing the federation behaviour would be a good idea
i can't seem to find the PR author's fedi account, their mastosoc and mastonline accounts seem for testing only, so I can't mention them
@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. [参照]
@helene @trwnh @Claire Note that Fedibird currently sends an EmojiReact activity for Unicode emoji and a Like activity for custom emoji for compatibility purposes.
This causes the problem that when you react to vanilla Mastodon with Unicode pictograms, the recipient does not notice it at all.
There is a way to fix this in Mastodon to interpret EmojiReact activity as Favourite.
A better solution is to merge Fedibird's EmojiReaction into Mastodon.
@noellabo @trwnh @Claire Pleroma and Akkoma interpret and send EmojiReact. Misskey and Akkoma can interpret
EmojiReactwith custom emoji with the content field and anEmojitag. Pleroma does not handle custom emoji yet, only unicode emoji. Both Pleroma and Akkoma translate Like activities with_misskey_contentinto EmojiReact, to ensure compatibility with Misskey.Using the Like activity with custom emoji for compatibility purposes does not seem required anymore, as Akkoma and Misskey understand
EmojiReactwell. I will try to support custom emoji reacts on Pleroma as well, to ensure full compatibility.I have considered aliasing
EmojiReacttoas:Likein the JSON-LD@contextfor Mastodon compatibility, but this does not seem like a good idea. If there is interest in merging Fedibird’s implementation into Mastodon, it would be wonderful!