Ooh, would you look at that? A verified link on my Mastodon account via rel=“me” (available in 2.6.0+) :)
(If you already had the rel=“me” in place before upgrading to 2.6.0, edit and save your profile again for the verification routine to run and update your profile.)
(Mind you, since you can self-host Mastodon, you should really verify links yourself instead of relying on a cosmetic feature as I could have just faked that via a bit of CSS.) ;)
@aral @KevinMarks Plus, if you modify your instance CSS, then that's really just saying your instance is untrustworthy. Perhaps less significant too, when your instance is literally on the same domain as the link being verified... ;)
@trwnh @KevinMarks Hehe, true :)
@aral @trwnh @KevinMarks Each instance re-verifies locally. You could fake on your public profile, but local view on e.g. my instance would show the correct result.
@Gargron @aral @trwnh that's great! Looking forward to other instances upgrading and other fediverse codebases adopting rel=me verification too. #Indieweb #yesvember
@Gargron
How it's possible that a link is flagged as verified on an instance and not in another one? Both can check verified links.
@aral @trwnh @KevinMarks
@KevinMarks
I use values from the API. I can't use the plugin to check for the remote account?
@Gargron @aral @trwnh
@KevinMarks
And the plugin can't help here. I added manually "rel='me' to force a catch of URLs. But all fail, I guess due to the fact it's a remote account. @Gargron @aral @trwnh
@aral defaults matter. This showing up encourages people to build the rel=me bidirectional links