The permissioned data proposal has the concept of membership, but leaves it to the app to orchestrate it. The arbiter is our idea for a general-purpose, interoperable ATProto group membership service.
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 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 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.
The Atproto Spaces Alpha is Live - AT Protocol
Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
The Atproto Spaces Alpha is Live - AT Protocol
Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
The Atproto Spaces Alpha is Live - AT Protocol
Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
Arbiter Progress Report 2 - Zicklag's Leaflets
A new policy-based arbiter prototype and a draft of an interoperable lexicon for group servers.
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 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.
I just finished a progress report / summary of the arbiter server that we've been working on at @roomy.space. The goal is to have an interoperable standard for group membership management on top of the ATProto permissioned space proposal. The last couple weeks were full of progress & discussion!
Arbiter Progress Report 1 - Zicklag's Leaflets
zicklag.leaflet.pubAt @roomy.space we've been cooking up the design for the next, ATProto-native iteration of Roomy, and that includes private data on protocol! The first component that we're working on is a group membership service that we're calling the "arbiter". Here's full overview of the design so far!
The Arbiter - Group Management for Permissioned Spaces and Beyond
zicklag.leaflet.pubI have just finished an interactive arbiter simulator that runs right in the browser! The arbiter is our attempt at an interoperable group management system for the ATProtocol and permissioned spaces. zicklag.github.io/leaf-0.4/arbiter-simulator/
