Conversation

Notices

1. Christine Lemmer-Webber (cwebber@octodon.social)'s status on Wednesday, 02-Oct-2019 20:32:18 UTC Christine Lemmer-Webber

   • Emacsen

   @ckeen (looping in @emacsen who is busy but also knows things)

   The identity/name is the same no matter where the datashards object lives. (You can compose together some hints of where the data lives on another layer.)

   But maybe you are asking how datashards could be applied to making an activitypub actor "change servers". (cotd ...)

   • Christine Lemmer-Webber (cwebber@octodon.social)'s status on Wednesday, 02-Oct-2019 20:34:17 UTC Christine Lemmer-Webber

     in reply to

     • Emacsen

     @ckeen @emacsen What you would do is have the mutable datashards object point at a different inbox. So the first revision of the mutable datashards object would point the inbox at socialfoo.example, then if we want to move it, we switch the inbox to socialbar.example *on the stored datashards object*.

     That allows us to "change our activitypub server" through a mutable datashards object.

     The update will have to be propagaged across the AP network, yes. There's debate on how to best do that.

   • Christine Lemmer-Webber (cwebber@octodon.social)'s status on Wednesday, 02-Oct-2019 20:34:28 UTC Christine Lemmer-Webber

     in reply to

     • Emacsen

     @ckeen @emacsen Hope that helps!