Hi,
I'm trying to use Mastodon's move feature to move fully over to Microblog.pub.
Mastodon says that the microblog.pub account is not an alias of the Mastodon account. I have set also_known_as = "me@microblog.example.com". Am I right in guessing Mastodon is looking in the webfinger response for the alias? It isn't listed in the alias part of the JSON response.
I'm not sure if this is a bug or a setup issue on my side. The webfinger aliases are URIs, so perhaps Mastodon is looking somewhere else for the acct format?
Thanks, Aonrud
Hey,
The
also_known_as
should be your Mastodon handle. If the doc is misleading, I will try to fix (I am open to suggestions too).Mastodon will check in the ActivityPub actor, not in the webfinger response.
Let me know how it goes, thanks!
Ah, sorry, that's a mistake in my post. I did set also_known_as to the mastodon handle. I just checked the JSON response from the root URL and it does contain "alsoKnownAs": [ "me@mastodon.social" ], so I guess the issue is on Mastodon's end. I saw some bug reports about caching on their end, but they seemed to be resolved and I had waited a couple of days, but I assume that must be the issue.
Thanks for your help! Apologies for the unnecessary ticket.
Aonrud
Actually I think there's mistake in the doc, the
also_known_as
should be the "ActivityPub ID".Can you run
inv webfinger username@domain.tld
with your mastodon handle and use that URL as thealso_known_as
?Thanks!
I get it -- I thought the webfinger was just to ensure the servers were aware of each other. Setting
also_known_as
to the ID URI works; Mastodon has accepted the move now.A note for anyone coming across this issue: if you add a redirect in Mastodon and then later want to move, it seems you have to turn off the redirect first, or it will give the error "[ID] is the same account you have already moved to".
Thanks ~tsileo!
Thanks for reporting the issue, I fixed the documentation: https://docs.microblog.pub/user_guide.html#moving-from-another-instance