For a mastodon account, if the proof is https://doma.in/@user/postid instead of https://doma.in/@user, it would have https://doma.in/users/user as backlink instead of https://doma.in/@user/. This is trivial and will redirect to the same page, the only problem is that mastodon verification badge does not work anymore because it can only recognize the format of https://doma.in/@user/.
Same thing on Sharkey, if the proof is a link to a post, the profile backlink will be reformatted as https://shar.key/users/userid. This will break the verification badge as well.
If you would like to take a look at an example, here's my profile: https://keyoxide.org/openpgp4fpr:996735be496180afb582ecabee31bb28ecf6b268
Thank you!
For a mastodon account, if the proof is `https://doma.in/@user/postid` instead of `https://doma.in/@user`, it would have `https://doma.in/users/user` as backlink instead of `https://doma.in/@user/`. This is trivial and will redirect to the same page, the only problem is that mastodon verification badge does not work anymore because it can only recognize the format of `https://doma.in/@user/`.
Same thing on Sharkey, if the proof is a link to a post, the profile backlink will be reformatted as `https://shar.key/users/userid`. This will break the verification badge as well.
If you would like to take a look at an example, here's my profile: https://keyoxide.org/openpgp4fpr:996735be496180afb582ecabee31bb28ecf6b268
Thank you!