Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ActorMove && InstanceMove activity #3

Open
CutestNekoAqua opened this issue Aug 4, 2024 · 0 comments
Open

ActorMove && InstanceMove activity #3

CutestNekoAqua opened this issue Aug 4, 2024 · 0 comments
Assignees
Labels

Comments

@CutestNekoAqua
Copy link
Member

ActorMove: Goal is to implement a activity that federates the transferal of a Actor like a User. The private and public key of the user shall not change to keep previous messages signed validly. API endpoint changes are to be federated, the id is to be kept the same, the name can change. If the new user is already existing (it should be able to be fetched during Move at least), like in AP, the new user needs to link back to the old user using a also known as field.

InstanceMove: Notice that a whole instance is migrating to a (new) domain. This activity can also be used to migrate from one versia software to another by only changing endpoints but keeping the domain the same. it is supposed to include a array of ActorMove activities in bulk for every existing actor on the instance.

Maybe optionally let other instances repeat a received instancemove activity to all known instances, if received for the first time, so that all instances on the network get notified about it at some point. (not sure if this is necessary)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant