OpenFederation

Signing in to the fediverse with your own account

Since 18 November you can sign in to a Mastodon server and to this publication with your Bluesky or OpenFederation account. How it works, what we tested, what broke and where it stops.

Misa Nikolic · · 3 min read

This week we connected OpenFederation to the fediverse, the identity part of it. Since 18 November 2026 you can sign in to a Mastodon server and to this Ghost publication with an AT Protocol account: one from an OpenFederation server, or your Bluesky account. There is nothing to create there first and no new password to remember.

How it works

OpenFederation was always meant as an identity layer: it answers who you are and leaves the posting to others. Mastodon, Lemmy and Ghost don't speak AT Protocol, but they do speak OpenID Connect, the standard behind most "Sign in with…" buttons. So the OpenFederation server (the PDS) learned to be an OpenID Connect provider. Think of a hotel reception: the hotel checks the passport you bring and writes the passport number in its book, not the name you'd like to be called.

In practice the app sends you to pds.openfederation.net. If your account lives there, you type your password. If it lives on Bluesky or another server, you're sent there to approve and then come back. The app gets your DID, your handle and display name, plus an email when the server has a verified one. It never gets your password, and posts stay wherever you write them (we don't copy content between networks).

The DID is the passport number. Handles change, and one that is given up can be claimed by someone else, whereas a DID is never reused. So the app remembers you by the DID.

What we tested

  • A lab first: a local Mastodon 4.5.8 and Lemmy 0.19.18 against our production server. Mastodon found an OpenFederation community straight away. Lemmy refused it because of one empty field in what we publish (endpoints: {}), a one-line fix.
  • Then mastodon.openfederation.net: signing in with a Bluesky account and with an OpenFederation account, and signing in again lands in the same Mastodon account.

Then this site, Ghost 6 on a small Google Cloud server with its own ActivityPub service. Readers sign in with Bluesky or OpenFederation, staff sign in to Ghost's admin with OpenFederation, and Mastodon can follow the publication.

What broke

Mastodon was the first surprise. It builds the username from the account identifier and, when there is no email, a placeholder address as well. A DID has colons in it (did:plc:…), so the placeholder was not a valid email and Mastodon gave up with "Error creating an account for this identity". We now give apps the same DID without the colons, in a separate claim (did_slug). When I signed in with my own Bluesky account, Mastodon made me plc_svyqejp7a6te7uuouvt3leqb. Not pretty, but that's the passport number again, and nobody can take it over by registering my old handle.

Ghost had no OpenID Connect sign-in at all. A community bridge exists, but it signs staff in by writing session rows into Ghost's database, so we wrote a small bridge for readers and used Ghost's official SSO adapter for staff. Email was the other recurring problem. Bluesky doesn't share your address, so Mastodon and Ghost ask for it once and confirm it with a link.

Where it stops

There is no firehose, the live feed Bluesky uses to index posts, which only matters if OpenFederation content should show up in Bluesky's apps. Lemmy supports this kind of sign-in only from 1.0, still in beta. And this publication is @index@ghost.opennewsrooms.com on the fediverse, because Ghost fixes that name (we checked).

The bigger one: our identities aren't listed in plc.directory, the directory most AT Protocol apps read. The tool to do it is ready, but nothing written there can be erased; a DID can be switched off, while its history stays public. We are still creating test accounts, so I'd rather wait until we aren't.

Both demos are open. Sign in at mastodon.openfederation.net or here with your Bluesky account, and follow @index@ghost.opennewsrooms.com from Mastodon. The code is in the openfederation-pds repository on GitHub. Feel free to ping us at hello[AT]opennewsrooms.com with questions or ideas.