Erm… concerning the `fediverse:creator` #OpenGraph tag in #Mastodon, described in :
-
Erm… concerning the `fediverse:creator` #OpenGraph tag in #Mastodon, described in <https://blog.joinmastodon.org/2024/07/highlighting-journalism-on-mastodon/>:
It's either not an OpenGraph tag (which would be unfortunate), or the example in the blog is wrong.
OpenGraph, being based on #RDFa, uses the `<meta property="…">` attribute, not `name`.
Also, if it is OpenGraph, the what namespace should I add for the `fediverse:` prefix to point to?
Which one is true for this feature, @MastodonEngineering?
-
beaware@social.beaware.livereplied to nik@toot.teckids.org last edited by
@nik @MastodonEngineering here's more information that could help
Add support for `fediverse:creator` OpenGraph tag by Gargron · Pull Request #30398 · mastodon/mastodon
A new OpenGraph tag to highlight article writers and website creators on Mastodon. Putting on a web page will allow Mastodon to link dir...
GitHub (github.com)
-
nik@toot.teckids.orgreplied to beaware@social.beaware.live last edited by
@BeAware @MastodonEngineering Sadly, the very question I asked is also unanswered in this issue. @trwnh asked the same thing in https://github.com/mastodon/mastodon/pull/30398#issuecomment-2126215768 , and none of what they said got respected as it seems.
-
beaware@social.beaware.livereplied to nik@toot.teckids.org last edited by
@nik @trwnh the issue of them not respecting opengraph is answered though? You know how it's used based on the link, it just doesn't change the fact that it's not respected.
Mastodon has a habit of not respecting standards. They barely respect AP.
I thought your question was directly asking how to use it. Not if it would change to respect opengraph?
-
trwnh@mastodon.socialreplied to beaware@social.beaware.live last edited by
-
trwnh@mastodon.socialreplied to nik@toot.teckids.org last edited by
@nik @BeAware @MastodonEngineering fwiw the example is wrong, it should be meta name= because it is inspired by Twitter Cards. the reason it was expressed as property= incorrectly is because mastodon currently makes no distinction between the two and will grab either one if available, even if they are different values.