The entire point of ActivityPub is that it’s open and EEE-proof. If the users leave it for something proprietary but better, then it isn’t EEE, it’s just a better product.
Simply being open source is not an achievement in itself. The platform has to be user friendly, stable and future-proof. Most FOSS and federated alternatives create a platform and then endlessly harp on federation like that’s the end. No, that’s the beginning. The point is to make a product better than Big Tech WHILE maintaining federation and Foss status. THAT is what makes a platform EEE proof.
If the users leave it for something proprietary but better, then it isn’t EEE, it’s just a better product.
That’s literally the second E, extend.
Nothing is EEE-proof. If Meta puts even just 10 billion dollars into developing and marketing their fediverse EEE project, it’s going to be better for the average user (I.e: billions of people already using Meta’s services) than what a couple of FOSS devs made for free in their spare time.
That’s not what extend means in this context. In this context, extend means to add non-standard features to the protocol which only your implementation understands.
If they embrace ActivityPub and then start adding their own proprietary features that are enough for users to switch over, and Mastodon doesn’t, then it’s not an “evil agenda”, it’s Meta adding an essential feature that the users want and Mastodon isn’t able to add and ultimately Meta making a better product.
If Mastodon or Lemmy are truly superior and the future, then the product should be the best in the market, not DUE to federation but DESPITE it.
That’s one thing that everyone here forgets because right now federation is hard to get into, and the only people here are those who put the effort in because they believe in federation. That is the reason for their tolerance in an inferior product. But if that’s the case, then it will never be mainstream as long as the product is inferior.
The entire point of ActivityPub is that it’s open and EEE-proof. If the users leave it for something proprietary but better, then it isn’t EEE, it’s just a better product.
Simply being open source is not an achievement in itself. The platform has to be user friendly, stable and future-proof. Most FOSS and federated alternatives create a platform and then endlessly harp on federation like that’s the end. No, that’s the beginning. The point is to make a product better than Big Tech WHILE maintaining federation and Foss status. THAT is what makes a platform EEE proof.
That’s literally the second E, extend.
Nothing is EEE-proof. If Meta puts even just 10 billion dollars into developing and marketing their fediverse EEE project, it’s going to be better for the average user (I.e: billions of people already using Meta’s services) than what a couple of FOSS devs made for free in their spare time.
That’s not what extend means in this context. In this context, extend means to add non-standard features to the protocol which only your implementation understands.
If they embrace ActivityPub and then start adding their own proprietary features that are enough for users to switch over, and Mastodon doesn’t, then it’s not an “evil agenda”, it’s Meta adding an essential feature that the users want and Mastodon isn’t able to add and ultimately Meta making a better product.
If Mastodon or Lemmy are truly superior and the future, then the product should be the best in the market, not DUE to federation but DESPITE it.
That’s one thing that everyone here forgets because right now federation is hard to get into, and the only people here are those who put the effort in because they believe in federation. That is the reason for their tolerance in an inferior product. But if that’s the case, then it will never be mainstream as long as the product is inferior.