one of the biggest mistruths i've seen about the fediverse is that it is based on specifications. fedi followed a couple of specifications a long time ago. now it is unregulated, based on whatever behavior mastodon happens to have. the specifications themselves don't provide an entire social media network, which is why there are so many extensions just to make it usable. the spec is the mastodon codebase
and even then, activitystreams borrows it's extension system from json-ld, an overcomplicated serialization format for RDF, which is just worse XML. this means that, in order to make activitystreams usable, you have to implement an overcomplicated schema system that nothing else uses

the fediverse is unstandardized and entirely based on whatever happens to end up being used in practice. it is violated as implementations please and extensions end up based on throwing shit at the wall waiting for something to stick

@mia so you're saying there's a chance some fedi platform can figure out individual blocking done right? 👀
Follow

@apophis

I don't think this is possible given the distributed-to-instances core design of ActivityPub.

It's no minor tweak as the core design assumes such decisions are going to be made outside the hands of the author.

@mia

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.