@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.pubMar 11, 2026 at 4:13 PM
calendar pt. 1: ATProtocol beyond AppViews - building [at] habitat
our approach to permissioned data (part 1!)
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.
calendar pt. 2: spaces, meet cliques! - building [at] habitat
permission-ed data without AppViews
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 3: Your Bucket, My Data - Daniel's Leaflets
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.
Reading Proposal 0016: What atproto’s “Permissioned Data” Actually Does - Nick's Blog
AT Protocol is public by default. Everything you write goes into a signed, archived, and rebroadcastable repository that anyone can read from and moves throu…
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.
@essentialrandom.bsky.social's livestream on Streamplace
Day 4 of Reading the ATproto permissioned data spec (dramatic)
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.
atproto made simple: granular permissions - underreacted
spaces, meet cliques! how we built a minimal calendar on pear (our permission-enforcing ATProto repo) and what we had to build to get there.
calendar pt. 2: buckets spaces, meet cliques!
habitat.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
