Skip to main content


at some point maybe it would be worth doing a fediverse thread breakdown of the ideas in ocappub https://gitlab.com/spritely/ocappub/blob/master/README.org and how the work has continued over at @spritelyinst because everything I wrote in 2019 is now super, incredibly relevant

(I am anticipating a crash/collapse of the fediverse in its current form at a not too distant future; hopefully we'll have more answers ready by then, but this is a multi-year project)
in the meanwhile the most important thing to do is to keep doing the work, because explaining things isn't as powerful as demonstrating them https://dustycloud.org/blog/if-you-cant-tell-people-anything/
in particular, the "Nation-State'ification of the Fediverse" section has turned out to be SUPER ON POINT

but also the discussion of how neo-fascists co-opt decentralization language while having no real interest in dispersing authority, the intro to ocaps, etc

but again, I stopped writing because I found it was hard to explain things to people... and demo'ing is better. In the meanwhile, the doc does do a good job of explaining the problem space that the @spritelyinst is solving.

HOWEVER, this is not to say we are "fixing ActivityPub" in two ways:

- the ideas can eventually be ported back to ActivityPub, the spec. however if the heavily-mastodon-flavored version of ActivityPub (MastoPub?) prevails I'm not sure it can be upended
- our main focus is on technical pieces built on OCapN, but activitypub backfill has been long planned. it's in the future though. it's not the critical path.
the blocklist/allowlist path for the fediverse is a band-aid. it's a doomed approach to moderation, and it always converges on centralization as it continues to run. I think the doc explains why that is pretty clearly.
turning to "the approaches that worked for email" is laughable, since email has only gotten super centralized over time.
And still, what has #email become but a despairing medium requiring layers of centralized and personally applied #filters, #rules and #algorithms to crudely finesse out 0.1% of “oh I want that” from the continual barrage of the #SpamPhishFraud firehose?

And we open only a fraction of what gets through—an error-prone daily routine.

Yet it’s #OpenProtocol, free, ubiquitous, and easy to use; it will outlive us all.

What lessons should we learn from it?
@llis every time someone comes up with a bright idea to reform email it usually means dropping some feature people need every day.
(Like restricting interaction by ocaps or like result the loss of public access, eg. "anyone can send me messages".)
Maybe web-of-trust could be closest to possible least amount o feature loss but it's extremely hard to boot up to be useful; and maybe ocaps want to be the next WoT, dunno. Seems pretty far away in the future.