Hello, I’m Simon Horrobin. I’m working on a couple of projects which are ATproto relevant… one to handle sport and health data, the other for managing publishing workflow. Both of these need privacy to varying degrees. I think about this in a few axes… who can create, view, edit, delete, grant, revoke, all over time and state.
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
Rashid Aziz: Extending ATproto for private data - ATProto Community
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.
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 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.
atproto made simple: granular permissions - underreacted
atproto made simple: granular permissions - underreacted
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.
A Model for addressing privacy on ATproto
When I first got involved with Northsky social, we knew we would have to eventually address the elephant in the room. How do we proactively protect a community from outside influences without relying purely on moderation? And more importantly, how do we keep bad actors from simply pulling their data straight from a relay?
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
NEW BLOG! After closely following atproto permissioned data, my take: what if an "atproto repository" is the base thing and there's more than one way to sync it? Based on @ipv.sx's take and grounded in a real-world Streamplace use case: how do I make a video private, then public?
What is an atproto repository?
iameli.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.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…
