I am concerned that Mastodon’s unary-vote system (favorites), and Lemmy’s binary-vote system (upvotes with downvotes) are mutually exclusive.
In a unary-vote system, a post’s vote count generally has little use beyond expressing the post’s absolute popularity/engagement, whereas, in a binary vote system, a post’s vote count can be used to gauge opinions, such as its level of quality, trust, or agreement. This difference in usage makes me concerned that the votes federated from Mastodon will water down the votes originating from Lemmy.
Currently, I can think of two possible solutions to this:
- Lemmy de-federates any votes originating from Mastodon (might be tricky as it would rely on all instances following suit)
- Add an option for the user to toggle within their settings allowing them to toggle off non-binary votes.
Removed by mod
Isn’t that the point of the “Add activity” (Section 6.6 of the ActivityPub Documentation)? I think it is equivalent to a “Favorite” in Lemmy.
This point feels moot, to me.
They already are compatible, though, aren’t they? That’s the whole point of the ActivityPub protocol. Mastodon, of course, won’t accept downvotes since, afaik, that is an extension made to the protocol by Lemmy, but likes/favorites/upvotes should federate normally.
Removed by mod
It will be interoperable up to the base spec (assuming, of course, that both services adhere to the base spec).
If both Mastodon, and Lemmy adhere to the spec, then they can interoperate. If Lemmy’s upvotes are federated as ActivityPub like activities, and Mastodon intereperets like activities as favorites, then there should be no issue. Downvotes will certainly not federate as Mastodon doesn’t use them, and they don’t exist in the base spec.
Likes federate as well. See Section 6.8 of the ActivityPub spec.