Feels more and more that all the so-called friends of #foss have fallen:
-
darth@silversword.onlinereplied to nilesh@fosstodon.org last edited by
-
beaware@social.beaware.livereplied to darth@silversword.online last edited by
@darth @nilesh well, to understand what we're saying, you have to understand a bit about AP.
AP is a standard made by the W3C group and has many different ways of doing things specifically for the goal of interoperability.
One of those being content types.
AP supports *several* different content types like "Articles", "Notes", "Audio", "Video", etc.
However, Mastodon only natively supports Notes and will convert *some* other content types to notes to make them easier to interact with, but they could have just supported those content types out of the gate if they wanted to.
That's why Lemmy and Mbin posts don't cross over well to Mastodon, for example.
They've done the same thing with the new Fediverse creator tag.
OpenGraph has a very specific way to do tags.
Mastodon does it their own way because they didn't want to have to answer to someone else. (OpenGraph)
They're very uncooperative.
-
darth@silversword.onlinereplied to beaware@social.beaware.live last edited by
-
beaware@social.beaware.livereplied to darth@silversword.online last edited by beaware@social.beaware.live
-
darth@silversword.onlinereplied to beaware@social.beaware.live last edited by
@BeAware @nilesh well that's kinda obvious, isn't it? I am on a Mastodon instance but we are not on Mastodon social media :gura_kekw:
But I get what you are saying. Many newcomers don't quite understand the federation concept at all, not to mention various software behind instances.
What I think would help Fediverse a little bit is to persuade publications to remove the "share to Mastodon" button from their articles and replace it with Fedi share button if the API is the same on all?
-
beaware@social.beaware.livereplied to darth@silversword.online last edited by
-
exerra@daedric.worldreplied to beaware@social.beaware.live last edited by
@BeAware@social.beaware.live @darth@silversword.online @nilesh@fosstodon.org The creator tag thing is a bit more complicated than that.
First of all we need to understand that OpenGraph isn't an open W3C standard. It was made by Facebook so URLs posted on Facebook can look prettier and have more info. It later went on to just become the de facto standard as, well, why reinvent the wheel.
Now with that explained, let's look at the actual tags. There is aprofile:username
tag in the OpenGraph docs, but it isn't used... at all... and it's uncertain why it exists, if there is already an expectation on what it should be and for what platforms the username would be given. Given it's a Facebook project, it might be meant for Facebook usernames, but, who knows, even they don't mention it.
So, instead of potentially breaking preexisting functionality and "taking over" a tag, they made a new one with the fediverse prefix. Seems like the safest option IMO, especially since with the fediverse prefix everyone (and every piece of code that looks for it) knows, without a doubt, that it is meant to be a fediverse username. -
beaware@social.beaware.livereplied to exerra@daedric.world last edited by
-
exerra@daedric.worldreplied to beaware@social.beaware.live last edited by
@BeAware@social.beaware.live @darth@silversword.online @nilesh@fosstodon.org Part of making standards and stuff like that is making sure that whatever you end up doing doesn't break preexisting expectations and code. That is why a bunch of standards are so messy - they can't disrupt existing behaviour, only add on to it.
Theprofile:username
tag is complicated in this regard because (1) you can't guarantee that you won't break any existing expectations & code, as well as (2) it's very ambiguous.
Every other OpenGraph tag has a clear usecase. The username tag on the other hand does not. If you are making something that uses it how can you tell what platform that username is meant to point to? Is it Facebook (most likely the idea when making it)? Twitter? Reddit? The same random blog/news site it comes from?
And your idea about formatting - how can you guarantee that the username is a fediverse username and not, for example, a defederated chat apps username (or even a fediverse clone that doesn't interoperate with the fediverse!)). You just can't, all you can do is guess.
Making a whole new tag with a very clear usecase is a much better solution than taking over a very ambiguous tag which may or may not break preexisting expectations and code. -
beaware@social.beaware.livereplied to exerra@daedric.world last edited by
Nik | Klampfradler 🎸🚲 (@nik@toot.teckids.org)
Erm… concerning the `fediverse:creator` #OpenGraph tag in #Mastodon, described in : 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 `` attribute, not `name`. Also, if it is OpenGraph, then what namespace should I add for the `fediverse:` prefix to point to? Which one is true for this feature, @MastodonEngineering@mastodon.social?
Teckids-Tooties (toot.teckids.org)
It's a simple formatting difference. Not a complete tag change.