The ability to make information private fundamentally conflicts with how ATProto is designed. All records have to be sent to all Relays and AppView nodes on the network to provide a "global view" of the network. So there's no way to keep records private without locking out some user's servers from viewing them, and since AppViews are centralized indexing services, they won't function without being able to see the entire network.

▲

NiallBunting an hour ago | parent [-]

Yeah, apps wouldn't be able to only listen to the firehose.

There are some proposals for private files. However, I'm outside the AtProto world so not sure what exactly the suggested implementations are. I just hope they give enough control.

I think the technology could potentially be used for way more than microblogging. I would love to use webapps that store the data on my devices and share it with specific people. The data and access under my control.

[1]: https://dholms.leaflet.pub/3mhj6bcqats2o

	▲	blackqueeriroh 2 minutes ago \| parent [-]
		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.