Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mastodon verification requires rel="me" in anchor #14

Closed
jtkristoff opened this issue Nov 13, 2022 · 3 comments · Fixed by #15
Closed

Mastodon verification requires rel="me" in anchor #14

jtkristoff opened this issue Nov 13, 2022 · 3 comments · Fixed by #15
Assignees
Labels
enhancement New feature or request

Comments

@jtkristoff
Copy link

For the Mastodon social link, it would be nice to be able to add a rel="me" tag into the anchor link ? This is used to perform link verification on the associated Mastodon account. More detail can be found here: https://docs.joinmastodon.org/user/profile/

This way I don't have to hack up the theme to much myself to add this in. Thanks kindly.

@gevhaz
Copy link
Owner

gevhaz commented Nov 13, 2022

Seems good to add. Thank you for the suggestion. Do you know of any downsides to adding it to all other social links as well? I think it makes sense for more or less all of them, and I don't think it hurts.

@gevhaz gevhaz added the enhancement New feature or request label Nov 13, 2022
@gevhaz gevhaz self-assigned this Nov 13, 2022
@jtkristoff
Copy link
Author

I can't think of any serious problems this would present. It seems sensible to just add it to all of social media links with the only downside it is a few extra bytes that go unused. I can't imagine anyone getting too upset about that.

@gevhaz
Copy link
Owner

gevhaz commented Nov 13, 2022

I added it to the master branch. git pull should give you the changes. Let me know if there are any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants