Only up-votes on posts and comments are federated. Is there a technical reason why (limitation of ActivityPub?) or is it a social reason?
Only up-votes on posts and comments are federated. Is there a technical reason why (limitation of ActivityPub?) or is it a social reason?
The issue is that ActivityPub, the protocol used for federation, wasn’t designed with reddit-likes in mind. Upvotes are repurposed Mastodon "favourite"s, and boosts are Mastodon’s equivalent of “retweets”, but downvotes are brand new with the appearance of lemmy/kbin. One could extend ActivityPub to have a new thing for downvotes, but non-lemmy/kbin instances like mastodon servers wouldn’t have any use for them.
Also, a not insignificant number of lemmy instances don’t have downvotes as a deliberate choice.
Is ActivityPub not open to arbitrary extensions? I thought it was a very loose spec and the only concrete spec is an agreement between instance types. But i’ve not looked at the protocol closely yet, despite developing around it hah.
You mean… embrace and extend?
Yes it can be extended but apps would need to be upgraded to make use of the new data flowing around. If they see an activity type they don’t understand they’ll just ignore it.
Expecting every different platform to all move in lockstep is not feasible so a situation where some support downvotes but some do not is going to have to be part of the process. Even if it was just kbin to kbin initially, that’d still be an improvement.
Yea, that is what i was thinking. I myself am working on some ActivityPub stuff and while compat is important to me, i also plan on potentially exposing new features in this manner. If other software wants to federate with it, cool, if not, whatevs. It’s data propagation, as with everything in ActivityPub it’s optional that consumers use it as desired.