What you linked is by Bluesky’s own staff - it’s him laying out the design plans for the protocol’s private data implementation.
He’s doing it to engage publicly with the community, since many of us also build on the protocol.
He’s doing it to engage publicly with the community, since many of us also build on the protocol.
It looks like this basically just reinvents ActivityPub (local servers can pull or push to remote servers). So it defeats all of the "benefits" you get from Bluesky's firehose-based approach anyway, except for the fact that Bluesky assumes you're going to be using their AppView and they will always have access to your private data.