like in the case where you assume that you maintain control over the previous domain and can do redirects and put a move validation key in a DNS TXT record for extra for-surezies i don't understand the problem. like shouldn't this be what instance metadata is for, advertise if you can understand xyz thing, if so, then we publish activity with the new domain, but otherwise we can keep using the old domain in the AP representation on the outgoing side and handle the redirects on the incoming side? continuously dismayed at how activitypub is literally built of linked data that is like pretty good at exactly this and we don't even have nostr levels of 'recognizing when a thing supports a thing' support.
no. bad masto. pointless restriction. have one way of validating activities and then do that one time. is this a ruby mental pattern? why does this codebase insist on doing everything everywhere. at the point when we are doing the side effects of the activity we should assume that it has already been validated
If you have a fediverse account, you can quote this note from your own instance. Search https://neuromatch.social/users/jonny/statuses/114720109506297671 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
