server: ability to accept moves #310

Open
opened 2022-12-28 22:35:47 +00:00 by Johann150 · 0 comments
Owner

This would require local users to be able to set the value of the alsoKnownAs field in the activitypub representation. In my mind there are still some open questions:

  1. Should we remove the alsoKnownAs value when the other actor is deleted?
  2. alsoKnownAs is an array, but do we want to allow users to migrate from multiple accounts at the same time?
  3. Do we want to allow users to remove an alsoKnownAs? (right away, after a time delay, ...)
  4. Do we want to check (after some delay) that the other actor has the respective movedTo value and warn the user if not?
This would require local users to be able to set the value of the `alsoKnownAs` field in the activitypub representation. In my mind there are still some open questions: 1. Should we remove the `alsoKnownAs` value when the other actor is deleted? 2. `alsoKnownAs` is an array, but do we want to allow users to migrate from multiple accounts at the same time? 3. Do we want to allow users to remove an `alsoKnownAs`? (right away, after a time delay, ...) 4. Do we want to check (after some delay) that the other actor has the respective `movedTo` value and warn the user if not?
Johann150 added this to the Account moves milestone 2022-12-28 22:35:47 +00:00
Johann150 added the
feature
label 2022-12-28 22:35:47 +00:00
Sign in to join this conversation.
No Label
feature
fix
upkeep
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FoundKeyGang/FoundKey#310
No description provided.