I've just finished the first, barely-working prototype of our new arbiter server! It's not ready for use just yet, but we're going to start experimenting with it in @roomy.space as a way to make every space a fully-fledged ATProto account that can be seamlessly managed by the Roomy space's admins.
Arbiter Progress Report 3
zicklag.leaflet.pubAug 10, 2026 at 6:11 PM
The Arbiter - Group Management for Permissioned Spaces and Beyond - Zicklag's Leaflets
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.
Welcome to the new atproto.com - AT Protocol
We've updated just about everything about atproto.com to make it easier for developers to just build things.
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.
At @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.pubThe ATProto community built a ton of great features and products over the past year. For our next trick, let's mature them into products and businesses.
Mosh Lee
(2/n) A feature solves one problem well — even delightfully well. But features get copied easily or absorbed into larger products. They have no distribution or adoption model. If your whole thing can become a pane in someone else's app, it's a feature.
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.pubAnother arbiter progress report! An attempt at a goups standard for ATProto. This week we talked to @habitat.network and it got us thinking about how we could inter-op, even with other projects that can't use the arbiter. Now we've got a draft lexicon that I'm hoping can work for both of us.
Arbiter Progress Report 2 - Zicklag's Leaflets
zicklag.leaflet.pubI love that the design of atproto was in part inspired by big social Kafka and ScyllaDB server backends and @martin.kleppmann.com's Designing Data-Intensive Applications and the community immediately used it to implement thousands of apps with no backend lol
I 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/
