@p @pwm @kallisti @nyx My guess is that Mastodon expected people to use the given activity’s Actor to discover the associated Actor; which is what Misskey does; but Mastodon doesn’t even do that itself, it removes the fragment from the keyId and uses that as an Actor URI.
I did bring this up last time I complained about actor discovery and HTTP signatures, and it led to this issue on the Mastodon side of things, which I would think is better behaviour.