permissionlessness so fucking cool every time to find out things like this after the fact
Rude1 Haunted Badness. ⁂
I used @microcosm.blue's lightrail.microcosm.blue tool to find all the Germ users so I can fix their records in our database. (Uncoordinated) teamwork makes the protocol dream work.
Apr 18, 2026 at 5:31 AM
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 Diary 6: Boring Auth - Daniel's Leaflets
In which we resist the temptation to invent a clever authorization model & pick the boring one instead.
B-Sides: Permissioned data is a love triangle - Nick's Blog
This is a B-sides post with unpolished thoughts that didn’t make it into the main article.
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...
Permissioned Data Shapes: Private Events - Nick's Blog
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 Interlude: Spaces - Daniel's Leaflets
In which I retcon the naming of everything.
greensky: what does permissioned data feel like? - building [at] habitat
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.
Authority as Possession: Permissioned Spaces Deserve Better Than ACLs
Why Capability Trees are the right governance primitive for permissioned spaces.
@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.comwhile we're here, here's how i wish permission sets were explained to me
atproto made simple: granular permissions
underreacted.leaflet.publooking for feedback on the first pass of permissioned data protocol lexicons! hop in & let me know your thoughts! discourse.atprotocol.community/t/permissioned-data-pds-lexic…
Permissioned Data PDS Lexicons
discourse.atprotocol.communityI really love how this handy widget lets you quickly browse through permission sets for various existing services Pro tip for lexicon designers: This is a great way to learn from peers -- @sifa.id, @beaconbits.app, etc -- who've done the work to decompose their permissions into useful subsets 😉
This is a good example of the permissionless innovation happening in the #Atmosphere: create an initial LinkedIn-style site you can access via your existing Bluesky/Blacksky/Eurosky/etc. account, then add more and more features leveraging your existing personal data in the Atmosphere and beyond.
Sifa ID 🪿
If you go to your personal Sifa Page at page.sifa.id/%3C@handle%3E/now, it now shows your personal heatmap and activitystream. (Check nownownow.com/about for the history of the /now page :))
