UnshavedYak

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.

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.

Yup. I’m trying to design (trying! lol) my own little slice of Fedi with this same problem in mind. Social networks exploited some natural tendencies towards toxicity for engagement. We need (imo) some people to explore ways to mitigate that.

What’s the difference to users of the two platforms, in your eyes? I’m not familiar with the workflows of either Instagram nor DA