Discussion across the Atmosphere
Permissioned Data Diary 6: Boring Auth - Daniel's Leaflets
Daniel's Leaflets · dholms.leaflet.pub
In which we resist the temptation to invent a clever authorization model & pick the boring one instead.
Read on dholms.leaflet.pub5 linkblog notes · 1 Leaflet comment · 9 Bluesky posts · 5 Semble saves
Discussion
-
Tim Disney @disnetdev.com
In which we resist the temptation to invent a clever authorization model & pick the boring one instead.
-
Kevin Wilson @khwilson.bsky.social
or what's missing from the permissioned data spec for ATProto to enable patients to have centralized access to (some of) their medical records
-
daniel holmgren 🫠 @dholms.at
In which we put records in a repo, sign them, and sync them (but not quite the way you think).
-
Nick Gerakines @ngerakines.me
AT Protocol is public by default. Everything you write goes into a signed, archived, and rebroadcastable repository that anyone can read from and moves through relays. This core design decision makes the network so legible and easy to build on, but it also blocks entire types of…
-
The Fulcrum by Reuben Walker ⚒️⛓️💥🏴☠️ @thefulcrum.eurosky.social
Welcome to your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism.
-
daniel holmgren 🫠 @dholms.at
auth: it's just a list! authorization tends to bring out Strong Opinions ™️ so we decided to try to keep it as simple as possible in the protocol & let the applications build higher-level abstractions give it a read & let me know your thoughts!
-
Private data is coming soon! @dholms.at has been keeping a diary about the design process
-
Jim Ray @jimray.bsky.team
@dholms.at (who coauthored the UCAN spec) went into a few more details about why we're not going that way with permissioned data in his latest diary
-
Pylon @bigkoala71.bsky.social
I don't really understand the technical details but I *think* the underlying protocol development allows for individual posts to be access controlled to a list of people. Which I think allows private accounts?
-
Ryan 🍠🍂 @pyry.lutefisk.online
this is great and I've been reading some related blog posts about it while my internet has gone back to 90s dialup due to the rain. anyway seems like we basically will get private posts from this too?
-
leite mosca @luan.bisca.net.br
acheeei
-
山貂 @yamarten.bsky.social
今週のリンク(1/2) #ATプロトーク * Bluesky素材 * PDSのアカウント管理画面リニューアル * Blueskyのgallary案 * permissioned dataの認証について * Todo: TODOアプリ * Resolution Roulette: ルーレットbot * atmo.garden: Bluesky上のコミュニティ形成
Saved in
-
juprodh @juprodh.me
-
-
Tim Disney @disnetdev.com
-
jacky! on da skyline @jacky.wtf
-
🬕🬢▌🬜🬎🬓🬕🬢▌🬴🬰🬃🬰🬴🬐 @nandi.uk
atproto’s permissioned spaces should use a boring core: one member list of DIDs controls read/sync access, while apps and space hosts layer richer rules above and below the protocol. Writes are judged by readers, not enforced by the protocol. Apps get short-lived, space-scoped…
Connections
-
Victoria @vicwalker.dev.br
this leads to Permissioned Data Diary 7: Off the Record - Daniel's Leaflets
-
Victoria @vicwalker.dev.br
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets leads to this