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

two rel attributes in website links confuses Mastodon, cannot verify links on ORCID profiles #6688

Closed
hardyoyo opened this issue Dec 5, 2022 · 9 comments

Comments

@hardyoyo
Copy link

hardyoyo commented Dec 5, 2022

It would be a nice-to-have feature if one could set up reciprocal links from a Mastodon profile to an ORCID profile. This requires that the link on the ORCID profile has a rel attribute, specifially "rel=me". It appears there is such an attribute:

<a rel="noopener noreferrer" href="{{website.url.value}}" target="website.urlName" rel="me nofollow noopener noreferrer">{{website.urlName != null? website.urlName : website.url.value}}</a>

However, this rel=me follows another rel attribute, and this is probably confusing Mastodon. Thus, adding an ORCID profile link from a Mastodon profile does not show up as a verified link in a Mastodon profile.

@hardyoyo
Copy link
Author

hardyoyo commented Dec 5, 2022

It's entirely possible this is perfectly valid markup, and the error is on the Mastodon side. Let me know if I should open a ticket there.

@hardyoyo
Copy link
Author

hardyoyo commented Dec 5, 2022

a relevant Stack Overflow article: https://stackoverflow.com/questions/39890586/multiple-rel-attributes

@pagiraud
Copy link

Don’t you think this is in fact the same issue as #6668 ?

@hardyoyo
Copy link
Author

Yes, though that issue is closed and the problem remains.

@pagiraud
Copy link

The issue is closed because it has been added to the roadmap.

@hardyoyo
Copy link
Author

Ah, I see, do you have a suggestion for a method of determining whether to report an issue, if it is observed and not found in the list of open issues? I will endeavor to follow it in the future. Closing this issue.

@pagiraud
Copy link

When I want to extend search to closed issues, I remove the words "is:open" in the search field.

@hardyoyo
Copy link
Author

Well, I'm happy it will get worked on at some point. And will try to remember to look for issues on your road map before I report them in the future.

@pagiraud
Copy link

Good to know, but I’m as involved as you in this project, no more, no less! :-)

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

No branches or pull requests

2 participants