After about twelve hours, the same post had received more than 300 shares and likes on Mastodon, while it had only been shared three times and liked four times on BlueSky.
-
@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
"but of the software provider that dominates the network to have control over servers and users"
why does mastodon.social have to write it. it's open source. anyone can. someone should have
"but I wouldn't say that I wish to impose standards"
you are though: complete compatibility is your demand
"I welcome diversity"
i don't if it means truth social
i welcome collaboration. there's no centralization in that
hmm, maybe the "it" was compatibility with GNU social?
that compatibility was in Mastodon from day one. it was there before ActivityPub came to exist.
but Mastodon decided to drop it, to break compatibility with other instances with diverse servers that still used the original Fediverse protocol
that's not collaboration. that's sabotage. and it was only possible because of the very centralization of power I'm speaking of.
-
@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
i say truth social not meaning literally truth social. i mean any maliciously inclined server, like "freeze peach" bigot ones
interoperability is the responsibility of parties interested in that. since it's open source, someone should write that. if mastodon software doesn't have something you demand, then write it. depending upon mastodon is your error, it is not mastodon's error for not satisfying your demand
and if it removes something that interoperability depends on?
and if it introduces incompatible features that break interoperability?
if they decide they don't wish to collaborate or cooperate, like they have in the past, is it my fault that they decided to make jerk moves?
why should I even bother to send merge requests that revert the removals or the incompatible features, if they've already made it clear they don't want them?
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net
-
hmm, maybe the "it" was compatibility with GNU social?
that compatibility was in Mastodon from day one. it was there before ActivityPub came to exist.
but Mastodon decided to drop it, to break compatibility with other instances with diverse servers that still used the original Fediverse protocol
that's not collaboration. that's sabotage. and it was only possible because of the very centralization of power I'm speaking of.it was dropped for any number of reasons. malice, incompetence, just not caring. and you want it. so you write it. and then it gets adopted
the double edge sword of open source is you can do whatever you want. but also there is no centralized hierarchy that is responsive to your demands
you do not pay mastodon. so they have no obligation to meet your demands
you're thinking in terms of business relationships. but there is none here. they can't disappoint you because they don't owe you
-
and if it removes something that interoperability depends on?
and if it introduces incompatible features that break interoperability?
if they decide they don't wish to collaborate or cooperate, like they have in the past, is it my fault that they decided to make jerk moves?
why should I even bother to send merge requests that revert the removals or the incompatible features, if they've already made it clear they don't want them?
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
So fork it
If the demand exists for the capability, your fork will be the new standard
Regardless, even if it doesn't become the new standard, anyone who wants what you also want can use your fork
You can't be disappointed because you're assuming a relationship that does not exist
Of course you *can* be "disappointed" but it carries no weight
-
@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
So fork it
If the demand exists for the capability, your fork will be the new standard
Regardless, even if it doesn't become the new standard, anyone who wants what you also want can use your fork
You can't be disappointed because you're assuming a relationship that does not exist
Of course you *can* be "disappointed" but it carries no weight
that's like saying we should fork threads or instagram or facebook. it wouldn't solve the interoperability problem that arises from intentional incompatibility from someone who has too much power and is willing to abuse it.
forking might give some choice to some instance operators, but it won't help the users who end up hurt in the cross fire of the jerk move, whether because they use an instance whose operator goes along with the jerk moves, or because they wanted to communicate with someone who does.
we have some safeguards because the software is free, and also because users can move.
but interoperability is not something that should be taken as lightly as mastodon has, and that it has because it could, because it was already big to care, big enough to start behaving like microsoft who figured they could reject ODF and force OOXML even while not being compatible with it; like google and facebook who interoperated through XMPP and then broke compatibility to make walled gardens.
if mastodon decides it wants to change the way users can move between instances, it could make it so that users could no longer move to instances that don't implement those changes, locking users in if/until other servers implemented compatible incompatibilities. that's the microsoft way, and it follows from having too much power. that power should be kept in check, not encouraged or defended.
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net
-
that's like saying we should fork threads or instagram or facebook. it wouldn't solve the interoperability problem that arises from intentional incompatibility from someone who has too much power and is willing to abuse it.
forking might give some choice to some instance operators, but it won't help the users who end up hurt in the cross fire of the jerk move, whether because they use an instance whose operator goes along with the jerk moves, or because they wanted to communicate with someone who does.
we have some safeguards because the software is free, and also because users can move.
but interoperability is not something that should be taken as lightly as mastodon has, and that it has because it could, because it was already big to care, big enough to start behaving like microsoft who figured they could reject ODF and force OOXML even while not being compatible with it; like google and facebook who interoperated through XMPP and then broke compatibility to make walled gardens.
if mastodon decides it wants to change the way users can move between instances, it could make it so that users could no longer move to instances that don't implement those changes, locking users in if/until other servers implemented compatible incompatibilities. that's the microsoft way, and it follows from having too much power. that power should be kept in check, not encouraged or defended.
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
i won't, and can't, argue with you about the history of a topic i know nothing about
but i do know that mastodon has plenty of interop with other software projects. do those other projects have the interop you desire? if yes, then mastodon sucks. if no, maybe there's a technical reason
did these older projects you allude to keep up to date with reasonable standards?
-
@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
i won't, and can't, argue with you about the history of a topic i know nothing about
but i do know that mastodon has plenty of interop with other software projects. do those other projects have the interop you desire? if yes, then mastodon sucks. if no, maybe there's a technical reason
did these older projects you allude to keep up to date with reasonable standards?
mastodon has introduced deviations from the standards, and others have been pretty much forced to adopt the deviations to be able to interoperate with users of the this big bully
the older project I alluded to was catching up, perhaps more slowly than ideal, and then mastodon spit on the plate it ate from since inception, and pulled the plug to kill the healthy interoperation
I'm not telling you this for you to hate mastodon, but to illustrate what can happen when too much power accumulates even in a free software project, to keep such powers in check and to stop promoting mastodon (instead of the Fediverse as a whole) as if getting mastodon further power were a good thing
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net
-
mastodon has introduced deviations from the standards, and others have been pretty much forced to adopt the deviations to be able to interoperate with users of the this big bully
the older project I alluded to was catching up, perhaps more slowly than ideal, and then mastodon spit on the plate it ate from since inception, and pulled the plug to kill the healthy interoperation
I'm not telling you this for you to hate mastodon, but to illustrate what can happen when too much power accumulates even in a free software project, to keep such powers in check and to stop promoting mastodon (instead of the Fediverse as a whole) as if getting mastodon further power were a good thing
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
But if these breaking changes were improvements, and the older projects were going slower at it, why haven't they caught up? Did they stop trying? What I am saying is should everyone be help hostage by the slowest project? It's not like we're in a monoculture. Plenty of projects have interop with mastodon
-
@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
But if these breaking changes were improvements, and the older projects were going slower at it, why haven't they caught up? Did they stop trying? What I am saying is should everyone be help hostage by the slowest project? It's not like we're in a monoculture. Plenty of projects have interop with mastodon
breaking interoperability is not an improvement. whether it's adding a feature in an incompatible way, or dropping an entire protocol, it hampers communication. how can one possibly frame the dropping of an entire protocol as an improvement? the Fediverse has multiple protocols, keeping compatibility with them is not a problem, dropping it is. it's not like any one of them is superior to the other, they're just different, and extend the reach of the Fediverse. Friendica and GNU social are not dropping protocols as they gain support for other protocols. diversity is good. if mastodon weren't the dominant player, these jerk moves would be losing it ground because it would be less able to interoperate. it's abusing its power.
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net
-
breaking interoperability is not an improvement. whether it's adding a feature in an incompatible way, or dropping an entire protocol, it hampers communication. how can one possibly frame the dropping of an entire protocol as an improvement? the Fediverse has multiple protocols, keeping compatibility with them is not a problem, dropping it is. it's not like any one of them is superior to the other, they're just different, and extend the reach of the Fediverse. Friendica and GNU social are not dropping protocols as they gain support for other protocols. diversity is good. if mastodon weren't the dominant player, these jerk moves would be losing it ground because it would be less able to interoperate. it's abusing its power.
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
"how can one possibly frame the dropping of an entire protocol as an improvement?"
if it is flawed
we drop protocols all the time with better protocols
"it's not like any one of them is superior to the other, they're just different"
i can't comprehend this argument. it is very true protocols have different capabilities, and some are objectively better than others
-
@lxo @Jirikiha @macacator @MyWoolyMastadon @oblomov @john @engel @everton137
"how can one possibly frame the dropping of an entire protocol as an improvement?"
if it is flawed
we drop protocols all the time with better protocols
"it's not like any one of them is superior to the other, they're just different"
i can't comprehend this argument. it is very true protocols have different capabilities, and some are objectively better than others
we're not talking about a single line of evolution of protocols, it's about entirely different protocols.
think SMTP (email) and XMPP (instant messaging). one doesn't replace the other.
think IMAP and POP. both serve roughly the same purpose, except IMAP offers a lot more possibilities, but discontinuing either one serves no purpose but prevent communication with servers that support one but not the other.
discontinuing support for Diaspora* or Status.Net or ActivityPub wouldn't make Friendica or Hubzilla better, it would just prevent communication.
imagine if Mastodon implemented AtProto (BlueSky) and then dropped ActivityPub. the former would increase interoperability, but the latter wouldn't make Mastodon better, it would just break compatibility with other ActivityPub implementations. it would fragment the Fediverse. that's what Mastodon did when it dropped Status.Net. it didn't make ActivityPub or Mastodon better, it just burned bridges. it kicked the ladder after climbing it. it's indefensible.
you can try by making up and pulling absurd, baseless arguments out of your hat, but that doesn't look great. it shows not only your ignorance, but also your blind faith on a project that has already shown not to deserve it, and your determination to defend its jerk moves by making things up.
CC: @Jirikiha@raphus.social @macacator@mastodon.social @MyWoolyMastadon@toot.community @oblomov@sociale.network @john@vyrse.social @engel@mastodon.social @everton137@vivaldi.net
-
The unofficial @FediTips can be very helpful in explaining the quirks of the various APIs in the fediverse.
@AlsoPaisleyCat @CarineMissiaen @luca @everton137
Carine, if you want any help with using this place please feel free to ask!
Also, there is lots of help on the website at https://fedi.tips
