Conversation

Notices

1. Embed this notice
   dansup (dansup@mastodon.social)'s status on Saturday, 06-Jun-2026 22:17:53 JST dansup

   What if

   dansup@loops.video

   could be

   @dansup.com

   Bring your own domain to Loops, migrate your full account across Loops servers.

   It's coming. Funded by @nlnet ❤️

   https://joinloops.org/roadmap

   #Loops #BringYourOwnDomain #FullAccountMigration

   • Embed this notice
     Holos Social (holossocial@mastodon.social)'s status on Sunday, 07-Jun-2026 06:33:07 JST Holos Social

     in reply to

     • Jörgi (chaos.social)
     • silverpill

     @joergi
     The custom domain and full account migration feature already works on Holos Social today. On Holos the keys are held by the device, so migration works even if a relay is down: nothing is lost. This is a different approach from a shared server that holds the keys for its users, and it is probably closer to the work of @silverpill on portable identity.
     https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
     @dansup

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Sunday, 07-Jun-2026 06:33:07 JST silverpill

     in reply to

     • Jörgi (chaos.social)
     • Holos Social

     @HolosSocial @joergi @dansup Holos with custom domains provides similar benefits but there is an important difference. In classic ActivityPub, identity is tied to a domain name. Keys are supposed to be ephemeral, and HTTP signatures are merely an optimization that servers use to avoid fetching every received activity by its id. In FEP-ef61, identity is tied to a DID, while domains are supposed to be ephemeral. If did:key is used, that key becomes a permanent part of every id.

     If you don't use FEP-ef61, a server can perform a MITM attack by serving a different actor document or a different key. FEP-ef61 protects against this (under the assumption that users controls their identity keys).

     The difference is subtle but it may matter a lot in some cases, such as when implementing E2EE.

   • Embed this notice
     Jörgi (chaos.social) (joergi@chaos.social)'s status on Sunday, 07-Jun-2026 06:33:08 JST Jörgi (chaos.social)

     in reply to

     • Holos Social

     @dansup

     Great you have that planned too, exactly what I wrote here https://chaos.social/@joergi/116693955340766744

     🤝

     I really hope that comes not only to loops, but also to #pixelfed, #mastodon and the #fedibridge.

     If you need inspiration, @HolosSocial has already implemented this, it works perfectly.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 09-Jun-2026 05:32:06 JST silverpill

     in reply to

     • Jörgi (chaos.social)
     • Holos Social

     @HolosSocial It should actually be relatively easy to implement client-side FEP-ef61 in Holos. If objects are served by the client, you don't need to implement client-to-server API (which is the most difficult part).

     @joergi