In which we put records in a repo, sign them, and sync them (but not quite the way you think).

In which we resist the temptation to invent a clever authorization model & pick the boring one instead.

Arguing against "universal spaces" and raising a couple questions that come up as a result.

In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.

A special edition of the data diary that sketches out the rough shape of where we're heading.

In which I retcon the naming of everything.

The third in a series of posts building up a solution to permissioned data on atproto. We look at two different models for where buckets live and why the simpler-looking one doesn’t work out.

The second in a series of posts building up a solution to permissioned data on atproto. We introduce buckets: a new protocol primitive for creating a shared social context.

The first in a series of posts about major design decisions along the way to a permissioned data protocol for atproto.

I’ve been meaning to break in my leaflet for awhile but haven’t gotten to it! Thanks to Phil (@bad-example.com) for voicing some concerns about the current work that we’re doing on PLC to support mirroring. It gave me a good reason to write up my thoughts on the technical improvements we have planned for PLC & to invite feedback/discussion from folks that are interested.