A look at Bluesky's proposed approach to private data on ATProto
Modeling communities on permissioned data - Daniel's Leaflets
Arguing against "universal spaces" and raising a couple questions that come up as a result.
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.
Rashid Aziz: Extending ATproto for private data - ATProto Community
Owning group data - meri's missives
Thinking about how communities can manage shared data on and off ATProto
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 PDS Lexicons
I wanted to share a first pass of the PDS lexicons for the permissioned data protocol to get some feedback while the paint’s still wet! You can check them out on my working branch: Comparing main...permissioned-data · bluesky-social/atproto · GitHub They’re all under the com.atproto.space namespace: atproto/lexicons/com/atproto/space at permissioned-data · bluesky-social/atproto · GitHub Confidence rating on Lexicons is probably like ~70-80%. Broad strokes, I think the shape is there. Though ...
AT Namespaces for Community Spaces
How should public community-controlled spaces be represented in atproto?
Early Permission Sets · bluesky-social atproto · Discussion #4437
Progress is coming along on "Permission Sets", as part of the atproto OAuth and permission system. As with other parts of the protocol, seeing how this functionality gets implemented for ...
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.
Playing with Parlances - Permissioned Data & AT Protocol - AT-WayFinding
Community privacy is one of our top priorities at @transrights.northsky.social which isn't possible out of the box with any ATproto implementation today that doesn't just hide an entire PDS. We're developing in the open and so I've published a proposal on it, feedback as always is we
Emerging from being "down in the technical weeds" of #atproto is a little mashup of @semble.so & WayFinder (wayfinders.network) Semble team released "open collections" this week - here we explore the "private & permissioned data" collection, created by @bmann.ca & now with 3 other contributors
@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.comPrivate & 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…
