Feels more and more that all the so-called friends of #foss have fallen:
-
Feels more and more that all the so-called friends of #foss have fallen:
#Google , #Mozilla , #Canonical , #Microsoft , #GitHub , #Mastodon , #RedHat ... the list goes on.
Who is really left? #Linux #Debian #postgresql ?
-
@nilesh what did Mastodon do?
-
@darth They've been holding #Fediverse back by not implementing interoperability standards. Been seeing too many instances of it. They come across as another wannabe-twitter kind of organization.
-
@nilesh @darth facts, and I worry hard that it's too late to stop it.
They don't respect AP or any other open standard they "seemingly" adopt.
See the latest "Opengraph" but not really Fediverse creator tag.
The most worrying concern for me is their refusal to add certain features because they just don't have to add anything they don't want, they already control the way 75% of users interact with Fedi. Like moderation tools, quote posts, and limiting replies.
-
Darth ŠČ! :arch:replied to BeAware :fediverse: last edited by
@BeAware @nilesh Yevgeniy convinced me that we are better off without the quote post thing, so I am in his camp now. I was not before. But I am kinda interested in these other things and why they matter. Why would anyone support AP (that's the bluesky one, right?) and why would BlueSky not simply start supporting ActivityPub instead?
EDIT: I mixed up AT an AP. I have no idea what AP is.
-
-
-
BeAware :fediverse:replied to Darth ŠČ! :arch: 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 ŠČ! :arch:replied to BeAware :fediverse: last edited by
-
BeAware :fediverse:replied to Darth ŠČ! :arch: last edited by [email protected]
-
Darth ŠČ! :arch:replied to BeAware :fediverse: 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 :fediverse:replied to Darth ŠČ! :arch: last edited by
-
Tom Casavantreplied to Darth ŠČ! :arch: last edited by
@darth @BeAware @nilesh I don't think there's a standardized way to share to a generic fediverse server yet, though I may be mistaken.
I know @stefan made this https://github.com/stefanbohacek/fediverse-share-button-wordpress awhile ago I don't know how many platforms it supports
-
@tom @darth @BeAware @nilesh Thanks for tagging me!
I just added a link to the FAQ section of a related project, which includes this information.
It was previously a bit buried, here's the direct URL: https://github.com/stefanbohacek/fediverse-share-button/#faq
-
Exerra :wee:replied to BeAware :fediverse: last edited by
@[email protected] @[email protected] @[email protected] 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 :fediverse:replied to Exerra :wee: last edited by
-
Darth ŠČ! :arch:replied to Stefan Bohacek last edited by
-
Exerra :wee:replied to BeAware :fediverse: last edited by
@[email protected] @[email protected] @[email protected] 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 :fediverse:replied to Exerra :wee: last edited by
https://toot.teckids.org/@nik/113153788695371329
It's a simple formatting difference. Not a complete tag change.
-
Stefan Bohacekreplied to Darth ŠČ! :arch: last edited by
@darth @tom @BeAware @nilesh Ha, thank you!
The big drawback of the original implementation of the button is its reliance on JavaScript, which is needed to determine which URL the site visitor should be redirected to based on the server.
With the WordPress version, that can be handled on the backend, so JS would only be needed to switch the logo, more of a nice-to-have feature.
I've just been a bit sidetracked with other things, but hoping to return to this over the next few days.