Colibri AppView

The AT Protocol AppView behind colibri.social.

The spaces alpha is unstable and explicitly not for production. Also, if you're reading this, you're here early. Howdy.

The architecture, the sync algorithm, the storage model, the moderation model and the full XRPC reference are documented at https://colibri.social/docs. This README covers running and working on the code.

Getting started

Requires Node 24 (.node-version) and pnpm.

pnpm install
cp .env.example .env   # then fill in the required values
pnpm dev

The AppView requires a few environment variables to boot: APPVIEW_DID, PUBLIC_URL, SIGNING_KEY, CREDENTIAL_ENCRYPTION_KEY, PDS_URL and COMMUNITY_HANDLE_DOMAIN. .env.example carries the openssl lines that generate the two secrets.

Layout

Package	What it does
packages/lexicons	Every Colibri schema, the space type declarations, and the types generated from them
packages/space	Client for com.atproto.space and com.atproto.simplespace: delegation tokens, DPoP-bound credentials, verified repo reads
packages/space-sync	Keeps a local copy of a space current: writer set, operation log, LtHash reconciliation, CAR recovery
packages/db	Drizzle schema and migrations for both libSQL and Postgres
packages/projections	Turns synced records into the typed read models the API serves
packages/identity	Service auth, DID documents, handle resolution
packages/community	Provisioning, credential custody, roles and permissions, access checks, moderation
packages/notifications	Notification indexing, Web Push and FCM
packages/blobs	CID-verified blob proxy for permissioned blobs, with image variants
packages/embeds	SSRF-guarded link previews and the GIF picker
packages/voice	mediasoup voice SFU
apps/appview	The server
apps/migrate	One-shot migration of repo-backed communities onto spaces

cp .env.example .env    # required, see Getting started
docker compose up --build

That runs the AppView alone on libSQL against the appview-data volume, pointed at whatever PDS_URL names. Three overlays compose on top of it:

Overlay	What it adds
docker-compose.postgres.yml	Postgres, and rewrites DATABASE_URL to use it
docker-compose.pds.yml	a local spaces-alpha PDS and a private PLC directory, for developing without a PDS of your own
docker-compose.integration.yml	the same PDS and PLC, ephemeral, for pnpm test:integration

docker compose -f docker-compose.yml -f docker-compose.pds.yml up

Commands

pnpm dev                # run from source, watching, no build step
pnpm build              # generate lexicon types and the pg schema, then compile
pnpm test               # unit tests
pnpm test:integration   # against a real spaces-alpha PDS, not run in normal CI
pnpm typecheck          # sources and tests
pnpm lint               # Biome

Lexicons

Every Colibri schema lives under social.colibri.beta.* while the spaces work is unstable, so it cannot collide with the social.colibri.* schemas already published from the pre-spaces AppView. The vendored com.atproto.space and com.atproto.simplespace documents are upstream and are never republished from here.

pnpm lexicons:codegen      # regenerate the TypeScript types from the JSON
pnpm lexicons:check-dns    # what DNS is missing before anything can be published
pnpm lexicons:publish      # publish to com.atproto.lexicon.schema records

DNS

An NSID resolves through a _lexicon TXT record on its domain authority, which is every segment but the last, reversed. So social.colibri.beta.channel.text resolves through _lexicon.channel.beta.colibri.social. One record per authority, thirteen in total. pnpm lexicons:check-dns prints the exact set, and takes an optional DID to check that each record points where you expect:

pnpm lexicons:check-dns did:plc:mprdjqjluoswa7awzggaggj3

Publishing

export LEXICON_PDS=https://colibri.social
export LEXICON_IDENTIFIER=colibri.social
export LEXICON_PASSWORD=<app password>

pnpm lexicons:publish --dry-run
pnpm lexicons:publish

Renaming the namespace

Promoting out of beta, or moving again:

pnpm lexicons:renamespace social.colibri.beta social.colibri --dry-run
pnpm lexicons:renamespace social.colibri.beta social.colibri
pnpm lexicons:codegen

Communities on other AppViews and other PDSes

A community record names its managingApp. That AppView holds the community's credentials and answers checkUserAccess for every one of its spaces, so it is the only one that can serve the community. A client that finds a community whose managingApp is not the AppView it is talking to must talk to that AppView instead, for reads, writes, events and voice alike. The field lives on the record rather than being read from the space policy because com.atproto.simplespace.getSpace only serves a policy to a caller already authorized for that space, and a prospective member is not. The profile space is public, so the record can be read before joining.

social.colibri.beta.community.create provisions an account on this AppView's PDS and needs PDS_ADMIN_PASSWORD. social.colibri.beta.community.adopt takes a DID that already exists, along with its password, and builds the community's spaces on whichever PDS already hosts it. The account keeps its DID, handle and PDS, and needs no admin password here. Its PDS does have to implement com.atproto.simplespace.

A password, not an app password: com.atproto.space.getDelegationToken requires full access. Passwords are stored AES-256-GCM encrypted under CREDENTIAL_ENCRYPTION_KEY. For a community hosted elsewhere there is no recovery path yet, because resetting the password needs that PDS's admin API.

Releasing

Three packages are published from here: @colibri-social/lexicons, @colibri-social/space and @colibri-social/space-sync.

A change to any of them needs a changeset:

pnpm changeset

A change to packages/lexicons is a protocol change. Treat it as a minor bump at least, because the client and the AppView both validate against it.