@geolaw @haubles @iftas Mastodon is aware of the problem, but although they get more funding than many other Fediverse projects, they are still short-handed.
General Discussion
1
Posts
1
Posters
3
Views
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@Edent embrace the diversity. 😜
-
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.mdSocialDocs says just an ID, no To nor CC.
https://socialdocs.org/docs/guides/account-migration/#the-move-activitySWICG says no ID, nor To, nor CC.
https://swicg.github.io/activitypub-data-portability/#process-0
-
The only bas part: posts would stay on old acc
-
You can do separate migrations, one at a time but yeah
-
@Edent It should work. But of course, there is a possibility of some popular implementation not being able to handle it.
-
@Edent - fun - just knowing this exists has me thinking of where to try it.
-
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?
-
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?
