You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm referring to two things here, first Mastodon's website verification, which Mastodon defines as:
"...All you need is a personal website that people recognize you by. When you link to this website from your profile, we will check that the website links back to your profile and show a visual indicator on it."
For this we would need to add an anchor tag to our website like the following one, but a link tag works perfectly fine too.
This is basically a way to get a check mark next to your website domain when you add it to Mastodon, thus confirming you own it.
Second it's the fediverse author tag, which allows web publications to be linked to a fediverse user when shared on Mastodon, this tag looks as follows:
Now, there's a bit of a discrepancy between these two features, the first one is supposed to be Mastodon exclusive while the second one, although introduced by Mastodon could in theory identify any user across the fediverse as the author of a web publication, so if they should be grouped under the same category is up for debate.
I add examples of valid tags for completion's sake.
By adding these tags by default in layouts/partials/metatags.html.twig users with the right entries in cecil.yml (or any particular page) could benefit of Mastodon's website verification and getting their username linked to their articles when shared to the fediverse (after they've done the proper configuration on Mastodon of course).
The documentation should be updated accordingly.
Describe alternatives you've considered
This can always be implemented in user-land after extracting Cecil's default templates of course.
Additional context
I made a working implementation here based on what it's already in place for Facebook and Twitter, we could discuss about how optimal it is and what changes are needed in case adding this makes sense.
The text was updated successfully, but these errors were encountered:
Related to a problem?
Hi Arnaud, allow me to explain myself.
I'm referring to two things here, first Mastodon's website verification, which Mastodon defines as:
"...All you need is a personal website that people recognize you by. When you link to this website from your profile, we will check that the website links back to your profile and show a visual indicator on it."
For this we would need to add an anchor tag to our website like the following one, but a
link
tag works perfectly fine too.Or
This is basically a way to get a check mark next to your website domain when you add it to Mastodon, thus confirming you own it.
Second it's the fediverse author tag, which allows web publications to be linked to a fediverse user when shared on Mastodon, this tag looks as follows:
Now, there's a bit of a discrepancy between these two features, the first one is supposed to be Mastodon exclusive while the second one, although introduced by Mastodon could in theory identify any user across the fediverse as the author of a web publication, so if they should be grouped under the same category is up for debate.
I add examples of valid tags for completion's sake.
Describe the solution you'd like
By adding these tags by default in
layouts/partials/metatags.html.twig
users with the right entries incecil.yml
(or any particular page) could benefit of Mastodon's website verification and getting their username linked to their articles when shared to the fediverse (after they've done the proper configuration on Mastodon of course).The documentation should be updated accordingly.
Describe alternatives you've considered
This can always be implemented in user-land after extracting Cecil's default templates of course.
Additional context
I made a working implementation here based on what it's already in place for Facebook and Twitter, we could discuss about how optimal it is and what changes are needed in case adding this makes sense.
The text was updated successfully, but these errors were encountered: