Curated Resource ( ? )
Permissioned data is a love triangle
Curated:
20/02/2026 from
ngerakines.leaflet.pub/3mf5wu6fs6225
my notes ( ? )
"ATProtocol already supports... Permissioned data ... a love triangle between the user, the identities they grant permissions to, and the applications [which] view controlled data".
Nick Gerakines first briefly summarises a previous post setting out how to build permissioned data into atprotocol: adding an optional service field pointing to "a service that uses inter-service authentication to provide the data. Apps that don’t support this feature won’t find the content ... Apps that do support it will control access with permissions."
Then he refines the model further, covering:
- "trust relationships needed ...
- why data portability must not be lost ...
- how a permission-aware PDS can join the network’s event stream without exposing record contents."
It then gets deep into the technology, of which I properly understood a fraction, including:
- "ATProtocol repositories already separate “what exists” from “what it contains”"
- so "a permission-enabled PDS shares... nodes without the record data blocks", so it's announcing “a record at this path was created or updated, here’s its content hash, but you’ll need to ask me for the actual content... from push to pull."
Read the Full Post
The above notes were curated from the full post ngerakines.leaflet.pub/3mf5wu6fs6225.Related reading
More Stuff I Like
More Stuff tagged atprotocol , community , permissioned data , unfinished , nick gerakines
See also: Bluesky and the ATmosphere , Online Community Management , Social Media Strategy , Politics , Communications Strategy