Again, another thread where two billion people joining our network and meeting us where we are … is somehow bad. If embrace extend extinguish is really the worry, then we have a bad protocol that needs extension to be usable by those 2B people, and we should fix that.
Extension implies that the protocol is missing some capability, otherwise it wouldn’t need to be extended. So we need to make the protocol better so they have nothing to add. If we don’t add those capabilities, ever, then the protocol is doomed to eventual irrelevance and wasn’t worth fighting over anyway.
You’re assuming some kind of objective point of view, but there are competing interests involved here. Those “capabilities” need not be things that are in the interest of the end users. For example, DRM, micropayments to unlock content, region coding, state censorship, etc etc etc. Bullshit that capital uses to exploit humans.
The protocol might well be complete and need no “extension” (as you mean the word) for us, and yet Meta might have many things they want to extend it to do. The whole point of this is, we have conflicting interests. Meta can push things that are not in their users interests because they have leverage. They hold our friends and their content hostage. And they lie and manipulate their users, who simply don’t care about things like this. Your idea that we are talking about our protocol vs their extensions competing on merits that appeal to users is just totally missunderstanding the objections.
I think you are getting too hung up on the term EEE. You think you know what the individual words mean, so you know what it’s all about. But a name is not the thing it represents. It’s just a name for a complex strategy that has been used successfully against us many times in the past. Rather than quibbling with the definition, you should probably spend some time reading the history.
Ah yes of course, a few people living off donations are supposed to outperform a multi billion dollar corporation in amount of features and polish within features.
The protocol doesn’t matter. Look at lemmy vs kbin. Kbin has “extended” features like microblogs & different UI. There’s plenty of people that like those features and thus are using kbin over Lemmy.
Just imagine kbin were much more attractive than Lemmy. More people would start signing up there. More people start “microblogging”. Maybe there’ll be other features introduced, and Lemmy can’t keep up with the nice things being added.
One day kbin decides not to federate with Lemmy at all anymore. Most people are on kbin at this point, Lemmy doesn’t have the same quality/amount of features. Now the average user has a choice: do they care about kbin being asses and leave kbin? No, of course not, not if the features really are nicer.
Now replace kbin with Facebook. Or Google, that’s exactly what they did with XMPP.
The only thing that is able to save from the triple E attack is the users actually caring enough about open platforms and deciding to not use the non-open ones. Or actually having more resources than Facebook, good luck with that.
In your scenario, Lemmy was worse than Kbin and didn’t suit users needs as well, and didn’t evolve the protocol fast enough to keep up. Kbin deserved to win in that case.
Nobody is saying it doesn’t “deserve” to win, whatever that means in a federated non-profit social network. The issue is that kbin probably wouldn’t be an asshole that intentionally created compatibility issues with lemmy just because they are in a superior position on the market in order to kill its ‘competition’. Meta absolutely will without a second thought.
The problem with that argument is that there’s value in something being not Facebook/Meta (or Twitter, or another corporate owned and run mega service), but that value isn’t as easy to demonstrate as “here’s a bunch of shiny features”, and once people are locked in, the focus shifts from improving the service to monetizing the service, making it rapidly worse for everyone.
People largely don’t think about how the services they use are structured, until any inherent structural issues come back to bite them. Twitter’s an obvious example, with people who were dependent on it for their livelihood from a networking/advertisement perspective ending up in trouble when the service went south. Reddit’s another example, although how that ends up is still TBD.
Again, another thread where two billion people joining our network and meeting us where we are … is somehow bad. If embrace extend extinguish is really the worry, then we have a bad protocol that needs extension to be usable by those 2B people, and we should fix that.
What follows is a non sequitur.
Extension implies that the protocol is missing some capability, otherwise it wouldn’t need to be extended. So we need to make the protocol better so they have nothing to add. If we don’t add those capabilities, ever, then the protocol is doomed to eventual irrelevance and wasn’t worth fighting over anyway.
Word is literally extended with intentional bugs, extensions will be arbitrary.
We can’t add those capabilities, because they will also be proprietary and under copyright or patent. If you try, Meta will just sue you for the lolz.
EEE is not about outcompeting someone.
You’re assuming some kind of objective point of view, but there are competing interests involved here. Those “capabilities” need not be things that are in the interest of the end users. For example, DRM, micropayments to unlock content, region coding, state censorship, etc etc etc. Bullshit that capital uses to exploit humans.
The protocol might well be complete and need no “extension” (as you mean the word) for us, and yet Meta might have many things they want to extend it to do. The whole point of this is, we have conflicting interests. Meta can push things that are not in their users interests because they have leverage. They hold our friends and their content hostage. And they lie and manipulate their users, who simply don’t care about things like this. Your idea that we are talking about our protocol vs their extensions competing on merits that appeal to users is just totally missunderstanding the objections.
I think you are getting too hung up on the term EEE. You think you know what the individual words mean, so you know what it’s all about. But a name is not the thing it represents. It’s just a name for a complex strategy that has been used successfully against us many times in the past. Rather than quibbling with the definition, you should probably spend some time reading the history.
Ah yes of course, a few people living off donations are supposed to outperform a multi billion dollar corporation in amount of features and polish within features.
The protocol doesn’t matter. Look at lemmy vs kbin. Kbin has “extended” features like microblogs & different UI. There’s plenty of people that like those features and thus are using kbin over Lemmy.
Just imagine kbin were much more attractive than Lemmy. More people would start signing up there. More people start “microblogging”. Maybe there’ll be other features introduced, and Lemmy can’t keep up with the nice things being added.
One day kbin decides not to federate with Lemmy at all anymore. Most people are on kbin at this point, Lemmy doesn’t have the same quality/amount of features. Now the average user has a choice: do they care about kbin being asses and leave kbin? No, of course not, not if the features really are nicer.
Now replace kbin with Facebook. Or Google, that’s exactly what they did with XMPP.
The only thing that is able to save from the triple E attack is the users actually caring enough about open platforms and deciding to not use the non-open ones. Or actually having more resources than Facebook, good luck with that.
In your scenario, Lemmy was worse than Kbin and didn’t suit users needs as well, and didn’t evolve the protocol fast enough to keep up. Kbin deserved to win in that case.
Nobody is saying it doesn’t “deserve” to win, whatever that means in a federated non-profit social network. The issue is that kbin probably wouldn’t be an asshole that intentionally created compatibility issues with lemmy just because they are in a superior position on the market in order to kill its ‘competition’. Meta absolutely will without a second thought.
EEE does not work by outperforming the OSS alternative. The extensions will be proprietary, and won’t be able to be ported to Lemmy.
The problem with that argument is that there’s value in something being not Facebook/Meta (or Twitter, or another corporate owned and run mega service), but that value isn’t as easy to demonstrate as “here’s a bunch of shiny features”, and once people are locked in, the focus shifts from improving the service to monetizing the service, making it rapidly worse for everyone.
People largely don’t think about how the services they use are structured, until any inherent structural issues come back to bite them. Twitter’s an obvious example, with people who were dependent on it for their livelihood from a networking/advertisement perspective ending up in trouble when the service went south. Reddit’s another example, although how that ends up is still TBD.