Link verification would work with Twitter profiles too since they have rel="me", but Twitter obfuscates links with t.co. I don't know how to deal with that, since resolving every href on the page to check for redirects doesn't seem viable.
Voluntary identity verification that does not involve real names or documents is fine, and more than that, it's extremely useful.
Nowhere on joinmastodon.org is there anything about "decommodification" or being "anti-brand", there's a section specifically aimed at businesses though
@Gargron But the rel=me is in the HTML, not at the other end of the link, right? So you would only have to follow links that have that attribute, not every link on the page.
@Gargron the trick I use is to rewrite twitter urls to the user intent page, which has a proper rel=me and an hcard. Eg twitter.com/intent/user?screenname=kevinmarks
@jalcine @Gargron so it is: http://www.unmung.com/mf2?url=https%3A%2F%2Ftwitter.com%2Fintent%2Fuser%3Fscreen_name%3Dkevinmarks&html=&pretty=on and looks like there is still a t.co link to follow, but it at least has rel=me on
@Gargron overall this is great! Thank you!
It isn't showing verification ticks for other mastodon instances (the circled ones are from https://github.com/Zegnat/verify-me-locally ) - also the redirection link at the top should have a rel=me on it too (and maybe a rel=canonical, though that is more aguable)
Another subtle thought - you could remove the rel=nofollow if the link is verified…
@Gargron do you verify links in a profile mirrored from another instance ? Or do you trust that instance to verify them and put them in the api?
@Gargron what triggers a verify check on a profile mirrored from another instance? eg if you follow xoxo.zone/@kevinmarks on mastodon.social, when will it check the rel-me links in that profile?
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!