[Simon_Gray]Hm... I'm trying to implement rel=me links, but Twitter intercepts my link back to my website, replacing it with its own t.co link that redirects to my website. This happens both when I put the link in the description and in the website filed. This makes the validation fail on https://indiewebify.me/validate-rel-me/?url=https%3A%2F%2Fsimon.grays.blog
Zegnat[Simon_Gray]: no, I do not think there is a way around it anymore that we know of. I think some RelMe parsers have opted to follow the redirect instead? Not sure how the indiewebify.me validator should handle this.
ZegnatIf you have any ideas how to overcome it, of course open a GitHub issue, put it in the wiki section, or just brainstorm here in chat :) I would recommend #indieweb-dev for that discussion though
[KevinMarks]rel-me resolution should always follow redirects; the issue is also that twitter removed the rel=me from their links (even on the intent page, where it lasted longer than the main user page)
[Simon_Gray]another question: how do people feel about including `mailto:` in rel=me? Isn't exposing your email address just an invitation to get spam?
[fluffy]On my h-card I provide my email address but random characters are %-encoded which is technically valid and trips up spam harvesters. Unfortunately it also trips up some of the h-card parsers.