add rel=me support #1037
Open
add rel=me support #1037
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is to support link verification in Mastodon. Mastodon does not have any equivalent to Twitter's blue-tick, so if you want to decorate your profile with some sense of authenticity, you can verify your profile to be associated with a particular URL: https://docs.joinmastodon.org/user/profile/#verification GitHub gained native support for this sort of verification sometime between last November and now, and so when you have a bidirectional link between your GitHub profile and Mastodon profile, the link to GitHub will be green. However, Twitter does not support rel=me, and is unlikely to. With this change, one can link their profile in their Mastodon bio using nitter.net/username, and for as long as their mastodon profile is linked back in the Twitter "URL" field, it will be verified. There have been similar attempts with "trusted" proxy URLs in the past, i.e. Twitter profile mirrors that are set up for the sole purpose of supporting rel=me verification. Those proxies are however unknown to most people, and the entire domain-based verification system kind of breaks down if nobody knows whether the domain can be trusted. People know nitter.net, however, and trust what is written on there to match what is written on twitter.com [1] Who knows whether the same is true for the unofficial Nitter instances, but I think one can ignore them for this purpose. Of course I can deploy this fork today on nitter.woodland.cafe and then verify `@[email protected]` against `nitter.woodland.cafe/untitaker`, but that's kind of pointless. [1] Whether it is really *known* may be debatable, but of all Twitter mirrors/proxies, I think nitter.net and maybe fxtwitter.com have the highest domain reputation and the best chance at making this kind of verification system work for Twitter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is to support link verification in Mastodon.
Mastodon does not have any equivalent to Twitter's blue-tick, so if you
want to decorate your profile with some sense of authenticity, you can
verify your profile to be associated with a particular URL: https://docs.joinmastodon.org/user/profile/#verification
GitHub gained native support for this sort of verification sometime
between last November and now, and so when you have a bidirectional link
between your GitHub profile and Mastodon profile, the link to GitHub
will be green.
However, Twitter does not support rel=me, and is unlikely to.
With this change, one can link their profile in their Mastodon bio using
nitter.net/username, and for as long as their mastodon profile is linkedback in their Twitter's "URL" field, it will be verified.
There have been similar attempts with "trusted" proxy URLs in the past,
i.e. Twitter profile mirrors that are set up for the sole purpose of
supporting rel=me verification. Those proxies are however unknown to
most people, and the entire domain-based verification system kind of
breaks down if nobody knows whether the domain can be trusted.
People know
nitter.net, however, and trust what is written on there tomatch what is written on twitter.com1
Who knows whether the same is true for the unofficial Nitter instances,
but I think one can ignore them for this purpose. Of course I can deploy
this fork today on nitter.woodland.cafe and then verify
@[email protected]againstnitter.woodland.cafe/untitaker, butthat's kind of pointless.
At the moment this is probably pointless to roll out though, because
nitter.netblocks a lot of datacenter ASNs due to intense scrapingefforts. So it would likely block all Mastodon servers.
Footnotes
Whether it is really known may be debatable, but of all Twitter
mirrors/proxies, I think nitter.net and maybe fxtwitter.com have the
highest domain reputation and the best chance at making this kind of
verification system work for Twitter. ↩