You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Inspiration: architecture ideas from Dan Abramov Open Social post #17
I already did up these rough diagrams the other week when explaining differences in the architectures we've ended up with, first image is more or less bluesky or AT Protocol's architecture, and the second is what we've essentially ended up with. I think there's probably a third necessary that can show the architecture that we expect this taskforce to enable or promote.
Reacted by Erlend Sogge Heggen, Arnold Schrijver, dclements and Bumblefudge
Additionally the ‘Nomadic ActivityPub’ spec by @silverpill makes a very compelling case for the nomadic identity capabilities required to match the ‘credible exit’ promise of atproto.
Together with that there’s also fep-7952, which I think can be retrofitted (at least in our reading of it, if not the actual spec) to describe a nomadpub-compatible instance.
The prime objective of the FEP is summed up pretty well here:
Unbundle the services and concerns of a typical instance
Sign everything: Recognize client-side cryptographic signatures as proof of authorship (by implementing FEP-8b32: Object Integrity Proofs), in addition to the current practice of relying solely on the instance URL.
B.Y.O. Actor ID: Using Object Integrity proofs enables Identity Hosting to be separated from the other instance concerns. Actor profiles can now be hosted separately from the instance (including as a static JSON object on a personal website), which in turn enables service providers to offer their users a “BYO (Bring Your Own) domain name” feature.
Separate Inbox/Outbox: (Optional) The previous steps enable message transfer and Inbox/Outbox hosting to be outsourced to separate service providers (the Actor profile links to these in the usual manner).
Separate Object and Collection hosting: (Optional) Similarly, AP Objects and Collections can now be stored on domains separate from the Actor's domain (since authorship and controller-ship can be proven cryptographically, in a domain-independent way). This enables the user to migrate storage service providers without having to change their Actor ID.
Bring-your-own Actor ID! 🪪💫
That’s really all I ever needed from the notion of a ‘single-user instance’. What I want to manage primarily on my own is just my identity, not a full AP server.
In this paradigm, someone’s tiny personal website could also be their Actor-ID Provider, and nothing more. That ID could in turn be used to as a (reasonably nomadic) account on any FEP-7952 compatible instance.
the idea is to detach the Actor object (which could be operated by a microserver that consumes almost zero resources, and basically just operates a big redirect table like a link-shortener) from the Service Provider, to be a little more like
email (in the use case where you point a domain that you own and configure at protonmail or mailgun or some other provider)
or SMS service (in that regulation enables you to keep your number when you switch phone co’s).
Dan Abramov's article was also discussed on HN with nearly 400 comments, some of whom make comparison with AS/AP and may contain good feedback: https://news.ycombinator.com/item?id=45388021
changed the title [-]Integrate architecture from Dan Abramov Open Social post[/-][+]Integrate ideas from Dan Abramov Open Social post[/+]on Oct 6, 2025
changed the title [-]Integrate ideas from Dan Abramov Open Social post[/-][+]Inspiration: architecture ideas from Dan Abramov Open Social post[/+]on Oct 6, 2025
Activity
[-]Integrate architecture from[/-][+]Integrate architecture from Dan Abramov Open Social post[/+]ThisIsMissEm commentedon Oct 3, 2025
I already did up these rough diagrams the other week when explaining differences in the architectures we've ended up with, first image is more or less bluesky or AT Protocol's architecture, and the second is what we've essentially ended up with. I think there's probably a third necessary that can show the architecture that we expect this taskforce to enable or promote.
erlend-sh commentedon Oct 4, 2025
Dan’s follow-up article Where It's at is also instructive.
Some other relevant notes from my conversations with @aumetra here:
..which boils down to:

erlend-sh commentedon Oct 4, 2025
Additionally the ‘Nomadic ActivityPub’ spec by @silverpill makes a very compelling case for the nomadic identity capabilities required to match the ‘credible exit’ promise of atproto.
https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md
Together with that there’s also fep-7952, which I think can be retrofitted (at least in our reading of it, if not the actual spec) to describe a nomadpub-compatible instance.
https://socialhub.activitypub.rocks/t/fep-7952-roadmap-for-actor-and-object-portability/4332
Proposal text
The prime objective of the FEP is summed up pretty well here:
Bring-your-own Actor ID! 🪪💫
That’s really all I ever needed from the notion of a ‘single-user instance’. What I want to manage primarily on my own is just my identity, not a full AP server.
In this paradigm, someone’s tiny personal website could also be their Actor-ID Provider, and nothing more. That ID could in turn be used to as a (reasonably nomadic) account on any FEP-7952 compatible instance.
aschrijver commentedon Oct 5, 2025
Dan Abramov's article was also discussed on HN with nearly 400 comments, some of whom make comparison with AS/AP and may contain good feedback: https://news.ycombinator.com/item?id=45388021
On Lobsters the article got 64 comments: https://lobste.rs/s/yh2bjm/open_social
TallTed commentedon Oct 6, 2025
s/big ass database/enormous database/ThisIsMissEm commentedon Oct 6, 2025
@TallTed these aren't official diagrams, just something I had existing from talking architectures with someone else.
[-]Integrate architecture from Dan Abramov Open Social post[/-][+]Integrate ideas from Dan Abramov Open Social post[/+][-]Integrate ideas from Dan Abramov Open Social post[/-][+]Inspiration: architecture ideas from Dan Abramov Open Social post[/+]evanp commentedon Oct 6, 2025
I'm not especially interested in duplicating someone else's architecture; my primary interest is in making the ActivityPub API easier to use.
erlend-sh commentedon Aug 30, 2026
We’ve done some exploration of at+ap identity interop in this thread: