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.
Permissioned Data Diary 2: Buckets - Daniel's Leaflets
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.
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
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.
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
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.
Permissioned data is a love triangle - Nick's Blog
Permissioned data is a love triangle between the user, the identities they grant permissions to, and the applications everyone uses to view controlled data. We don't need to change or reinvent the protocol to have it, because ATProtocol already supports it.
Permissioned Data Diary 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
The first in a series of posts about major design decisions along the way to a permissioned data protocol for atproto.
Permissioned Data Diary 6: Boring Auth - Daniel's Leaflets
In which we resist the temptation to invent a clever authorization model & pick the boring one instead.
Permissioned data on atproto — pick your depth
A private room in a place with no walls: how engineers are adding permissioned data to atproto. Read it plain-language or technical.
Permissioned data by dholms · Pull Request #94 · bluesky-social/proposals
This is an initial proposal for permissioned data. Details, terminology, and behaviors are all likely to change. For a friendly introduction to the protocol, check my my Leaflets. For discussion, f...
The Arbiter - Group Management for Permissioned Spaces and Beyond - Zicklag's Leaflets
The permissioned data proposal has the concept of membership, but leaves it to the app to orchestrate it. The arbiter is our idea for a general-purpose, interoperable ATProto group membership service.
continuing to build up our permissioned data protocol! this one asks what a bucket actually is and where the data that constitutes a bucket is stored. it argues for maintaining the atproto ethos in the permissioned data protocol as always, looking forward to hearing your thoughts!
Permissioned Data Diary 3: Your Bucket, My Data
dholms.leaflet.pubnew data diary! this is the most in the weeds yet, all revolving around our proposed URI structure for permissioned data. turns out you can figure out a lot about a protocol from the uri! as always, let me know what you think :)
Permissioned Data Diary 5: What’s in a Name?
dholms.leaflet.pub@dholms.at motivated me to make a follow up post on Stratos, @transrights.northsky.social approach to permission data on ATproto! This one is a bit of a brief technical overview and as a nice bonus, I've made the code base public.
Stratos: Lets get Technical
chipnick.com@eagraf.dev with part 1 of how we're building a personal calendar on ATprotocol and what we're thinking about (differently!) for permissioned data
calendar pt. 1: ATProtocol beyond AppViews
habitat.leaflet.pubPrivate & Permissioned Data
ATProto Private & Permissioned data
Habitat & permission spaces for organizations - building [at] habitat
Habitat's road to release: 03 ReBAC on spaces - building [at] habitat
Habitat's road to release: 04 Chalk - building [at] habitat
Habitat's road to release: 05 adopting opensocial - building [at] habitat
Permissioned Spaces Made Pretty — Lexidraw
atproto spaces repo export: feels a bit odd to do a giant index block. seems like this will put a low (and hard) cap on the number of record…
