In a way, it’s a bit harder for me to talk about the values and design goals of ActivityPub. It happened in a larger standards group and involved a lot of passing of hands. I think if I were to be robust about it, I would also ask Evan Prodromou, Erin Shepherd, and Amy Guy to weigh in, and maybe they should; I think it would be nice to hear.
The goal of ActivityPub to me, only partially realised in the decade since, was to function as a substrate to enable multiple social applications to exist within a single social graph; so that we could experiment with ideas other than (and perhaps radically different from) Twitter clones.
In some ways I felt that the C2S API was more important than S2S - the original drafts of the spec made S2S optional, but mandated C2S. Its funny and in some ways unfortunate how that flipped.
Strypey
Als Antwort auf Erin 💽✨ • • •"ATProto does not scale wide: it's a liability to add more fully participating nodes onto the network. Meaningfully self-hosting ATProto is a risk to the ATProto network, there is active reason to disincentivize it for those already participating."
#ChristineLemmerWebber, 2024
dustycloud.org/blog/re-re-blue…
Oof. That is *not* good for the claim that BlueSky's protocol can be as friendly to decentralisation and independent hosting as the fediverse.
IMHO that's game, set and match.
#BlueSky #ATProto
Re: Re: Bluesky and Decentralization -- Dustycloud Brainstorms
dustycloud.orgStrypey
Als Antwort auf Strypey • • •"In many ways, Bluesky is speedrunning the history of Twitter."
@cwebber, 2024
dustycloud.org/blog/re-re-blue…
This is exactly the comparison I've been making. Seeing it made within the context of a careful steelmanning of BlueSky's ATProto is very much a cat-that-got-cream experience for me.
Re: Re: Bluesky and Decentralization -- Dustycloud Brainstorms
dustycloud.org