Arbiter Progress Report 4 - Zicklag's Leaflets

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!

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!

Another 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.

while we're here, here's how i wish permission sets were explained to me

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.

Permission sets for bsky launched sometime early this year (and still have issues github.com/bluesky-social/atproto/issues…, github.com/bluesky-social/atproto/discus…). XRPC scopes were earlier, but as far as user communication goes it's not any better. Requesting one XRPC scope still looks scary for end users.

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/