A question about #ActivityPub account migration.

A question about #ActivityPub account migration.

Is it possible to use it to combine multiple accounts into one?

That is, can I `movedTo` all my old accounts to one new account, and set *several* `alsoKnownAs` on my new account's actor?

I mean, I see no reason why this wouldn't work. `alsoKnownAs` is an array of names.

I suppose if Alice is following both Bob and Chuck, then B & C are merged into Dave, she won't "double follow".

But I wonder if there are any other gotchas?

@Edent if the migration process is "detaching and reattaching a new public key/profile" to existing toots.... sounds like a fun but perfectly cromulent use case.

@Edent It should work. But of course, there is a possibility of some popular implementation not being able to handle it.

You can do separate migrations, one at a time but yeah

The only bas part: posts would stay on old acc

Three different #ActivityPub spec guides - three different answers!

FEP-7628 says a Move has an ID, To, & CC.
https://codeberg.org/fediverse/fep/src/branch/main/fep/7628/fep-7628.md

SocialDocs says just an ID, no To nor CC.
https://socialdocs.org/docs/guides/account-migration/#the-move-activity

SWICG says no ID, nor To, nor CC.
https://swicg.github.io/activitypub-data-portability/#process-0

@Edent embrace the diversity.

@Edent FEP-7628 is the only accurate spec. Move activity should be delivered to followers and have an ID (just like every other activity).

SWICG document is incomplete. SocialDocs website appears to be AI-generated.

@Edent yes

@silverpill@mitra.social socialdocs looks like Dan's work. If it is AI generated then that is a real disappointment.