why they’re bad? just ask claude. it ran into the same exact things i’ve ran into. until all of these are fixed imo its perfectly acceptable for developers to ignore permission sets. they’re just not baked until they’re understandable read this transcript: claude.ai/share/dbd3e30d-958d-4ac8-a3fc…
Claude
claude.aiApr 13, 2026 at 4:32 PM
Tyranny of Permissionlessness
open source’s narrow focus further empowers those with other ways to exclude
Auto mode for Claude Code
Really interesting new development in Claude Code today as an alternative to --dangerously-skip-permissions: Today, we're introducing auto mode, a new permissions mode in Claude Code where Claude makes permission decisions …
Authority as Possession: Permissioned Spaces Deserve Better Than ACLs
Why Capability Trees are the right governance primitive for permissioned spaces.
Platforms, Protocols, and Permissibility - writing.drewmca.net
A comparison of communication technologies across permission types
Permission set (#4108) · bluesky-social/atproto@f9dc9aa
* Export constants and type assertion utilities * Add permission set support to oauth provider * improve permission set parsing * Rename `PermissionSet` to `ScopePermissions` * Improve performa...
atproto made simple: granular permissions - underreacted
atproto made simple: granular permissions - underreacted
Claude says “You're absolutely right!” about everything | Hacker News
I'm fairly well versed in cryptography. A lot of other people aren't, but they wish they were, so they ask their LLM to make some form of contribution. The result is high level gibberish. When I prod them about the mess, they have to turn to their LLM to deliver a plausibly sounding answer, and that always begins with "You are absolutely right that [thing I mentioned]". So then I don't have to spend any more time wondering if it could be just me who is too obtuse to understand what is going on.
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.
greensky: what does permissioned data feel like? - building [at] habitat
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.
while we're here, here's how i wish permission sets were explained to me
atproto made simple: granular permissions
underreacted.leaflet.pubwhat if we made boring auth even more boring-er? if you're following along on permissioned data, give this a read & let me know your thoughts: discourse.atprotocol.community/t/removing-the-member-list/89…
Removing the member list?
discourse.atprotocol.communityHi, I hear you on this. There's a longstanding issue with Bluesky's more granular permission sets I'm hoping to get resolved, which is blocking Sill from implementing a better set of permissions. github.com/bluesky-social/atproto/issues…
Bluesky permission sets require inconsistent aud parameter · Issue #4850 · bluesky-social/atproto
github.comA deep dive on permissioned-data space access. The dials, policies, and the difference between handing out keys and revoking them.
Permissioned Data: Space Access
ngerakines.leaflet.pub
