執筆依頼があり、集英社オンラインで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
@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 EmojiReact
with custom emoji with the content field and an Emoji
tag. Pleroma does not handle custom emoji yet, only unicode emoji. Both Pleroma and Akkoma translate Like activities with _misskey_content
into 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 EmojiReact
well. I will try to support custom emoji reacts on Pleroma as well, to ensure full compatibility.
I have considered aliasing EmojiReact
to as:Like
in the JSON-LD @context
for 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!
@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
@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)
@trwnh @Claire @helene
That's right... Implements the ability to delete the specified reaction. At this time, if you refer to the EmojiReactions collection of the target Note, the deletion is reflected, so it is reflected remotely by the mechanism to synchronize it. Synchronized works by incentivities on the remote side who want to reflect all reactions. Also, when you delete it, reject Like or EmojiReact in the Reject activity.