Conversation

Notices

1. Embed this notice
   mcc (mcc@mastodon.social)'s status on Thursday, 31-Oct-2024 05:47:50 JST mcc

   • MrCheeze :retro:

   @MrCheeze this is a feature… until server X goes down. But server X going down is exactly what we are afraid of

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Thursday, 31-Oct-2024 05:47:48 JST mcc

     in reply to

     • Julian Fietkau
     • MrCheeze :retro:

     @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)

   • Embed this notice
     Julian Fietkau (julian@fietkau.social)'s status on Thursday, 31-Oct-2024 05:47:48 JST Julian Fietkau

     in reply to

     • MrCheeze :retro:

     @mcc @MrCheeze Define systematic infrastructure? Mitra exists as a practical implementation compatible with Mastodon, and it implements https://codeberg.org/silverpill/feps/src/branch/main/c390/fep-c390.md and https://codeberg.org/silverpill/feps/src/branch/main/ae97/fep-ae97.md. So you can divorce your identity from your AP instance today if you like. I just don't fully understand what that gets us.

     If you decide to take your Bluesky PDS down, does their relay keep serving cached copies of your posts forever? Is that a good thing, do we want that?

   • Embed this notice
     Julian Fietkau (julian@fietkau.social)'s status on Thursday, 31-Oct-2024 05:47:50 JST Julian Fietkau

     in reply to

     • MrCheeze :retro:

     @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.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Thursday, 31-Oct-2024 06:01:44 JST silverpill

     in reply to

     • Julian Fietkau
     • MrCheeze :retro:

     @julian @mcc @MrCheeze

     >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).

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Thursday, 31-Oct-2024 06:34:08 JST silverpill

     in reply to

     • Julian Fietkau
     • MrCheeze :retro:

     @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

     @mcc @MrCheeze

   • Embed this notice
     Julian Fietkau (julian@fietkau.social)'s status on Thursday, 31-Oct-2024 06:34:09 JST Julian Fietkau

     in reply to

     • silverpill
     • MrCheeze :retro:

     @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?

     Maybe I just need to read up on this more...

     @mcc @MrCheeze

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Thursday, 31-Oct-2024 06:51:10 JST silverpill

     in reply to

     • Julian Fietkau
     • MrCheeze :retro:
     • Mochikovski

     @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.

     @mcc @julian @MrCheeze

   • Embed this notice
     Mochikovski (mochi@mochi.mochikov.ski)'s status on Thursday, 31-Oct-2024 06:51:12 JST Mochikovski

     in reply to

     • Julian Fietkau
     • silverpill
     • MrCheeze :retro:

     @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.