Arbiter Progress Report 4 - Zicklag's Leaflets

In which we abuse permission sets to create virtual custom scopes for the arbiter.

Arbiter Progress Report 3 - Zicklag's Leaflets

The first arbiter prototype is live!

Arbiter Progress Report 2 - Zicklag's Leaflets

A new policy-based arbiter prototype and a draft of an interoperable lexicon for group servers.

Arbiter Progress Report 1 - Zicklag's Leaflets

Lots of implementation progress & lots of discussion with the community.

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.

Habitat & permission spaces for organizations - building [at] habitat

Our plans for organizational permissions on spaces

Habitat's road to release: 03 ReBAC on spaces - building [at] habitat

Fine-grained permissioning on top of spaces.

Habitat's road to release: 04 Chalk - building [at] habitat

The one where we don't release an API :)

Habitat's road to release: 05 adopting opensocial - building [at] habitat

This week, Habitat as a platform for organizational data is finally beginning to take shape. We've been working with other great atproto devs in the Communit…

Permissioned Spaces Made Pretty — Lexidraw

A drawing by @essentialrandom.bsky.social on Lexidraw

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.

Reintroducing Spaces - Daniel's Leaflets

Now with better perspective, zooming out and re-motivating the design of spaces, the new primitive for non-public data on atproto.

Habitat's road to release: 02 sap for syncing permissioned spaces - building [at] habitat

A package to help apps keep permissioned data up-to-date.

Habitat's road to release: 01 simplespace - building [at] habitat

First up: a pre-implementation of permissioned spaces

Permissioned Data: Space Access - Nick's Blog

Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.

Permissioned Data Shapes: Feeds - Nick's Blog

Public feed generators drink from a firehose that permissioned data never enters, so a feed that includes space content has to become a syncer, keep a live model of who can see what, and serve a different skeleton to every viewer.

Permissioned Data Shapes: Notifications - Nick's Blog

A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.

Permissioned Data Diary 7: Off the Record - Daniel's Leaflets

In which we put records in a repo, sign them, and sync them (but not quite the way you think).

proposals/0016-permissioned-data/README.md at main · bluesky-social/proposals

Bluesky proposal discussions. Contribute to bluesky-social/proposals development by creating an account on GitHub.