@julian@MrCheeze I don't think there's a systematic infrastructure for it. Bluesky on the other hand is built around a systematic architecture for that exact thing (although as I mentioned it has other decisions I don't like)
@mcc@MrCheeze I'm pretty sure there are people today running ActivityPub profiles on redundant servers or using distributed identities, but I have yet to understand how that works for post availability and retention, like how I would know where to go to read their stuff if the place I know them from is gone.
>Mitra exists as a practical implementation compatible with Mastodon, and it implements...
The main specification is FEP-ef61, which describes how decentralized ("nomadic") identity works. FEP-c390 is an older idea and it doesn't provide full data portability. FEP-ae97 is about combining FEP-ef61 with ActivityPub Client-to-server API.
>I just don't fully understand what that gets us.
You can clone your account to multiple servers, and those multiple accounts would work as one! And more: peer to peer, local-first applications. Mitra's implementation is actually incomplete, I recommend also checking out Streams, which supports FEP-ef61 and non-ActivityPub nomadic identity (Nomad protocol; this is where the "nomadic identity" comes from).
@julian I think servers should synchronize data between themselves, but the other approach where clients write to multiple servers (as they do in Nostr) is also fine
@silverpill Thanks, that helps me a bit. So I'd set up my client to send the posts I write to all of my multiple servers, and if one of them goes down I'm still reachable on the others with all my stuff? And the idea is that people who reply to me send their replies to all of my servers, or do my servers synchronize themselves on their own?
@mochi Unfortunately, handle is tied to a domain name. If primary gateway is dead, actor should update its gateways array, and thus obtain a new handle.
Actor ID ('ap' URL) is a permanent identifier that doesn't depend on a specific gateway.
@silverpill@mcc@julian@MrCheeze Sorry if this is not a right place to ask. I'm interested in FEP-ed61 but I'm stuck at Webfinger and gateways. What if a user only knows a webfinger handle alice@example.com but a gateway example.com is dead? The Webfinger section of FEP-ef61 reads like you somehow know the actor's gateway before you look up the actor.