In 2013, Google realised that most XMPP interactions were between Google Talk users anyway. They didn’t care about respecting a protocol they were not 100% in control. So they pulled the plug and announced they would not be federated anymore.
Basically keep people from using all the other platforms. Then stop supporting them. Similar like .docx never quite works in the open document editors. At least i refuse to believe that OSS devs are less skilled and motivated.
I’ve seen people bringing this up, but while they talk of EEE and XMPP, it seems like the analogy here is not being quite finished and formulated.
If we apply that to this, it seems like people are saying “if Meta changed the ActivityPub protocol to favor them and become incompatible with the rest of the Fediverse, Fediverse users would choose to return to Meta-owned platforms.”
And that’s what I’m questioning. Would you? Would you think others here would? I wouldn’t. I’d rather go to whatever fork Fediverse devs favor instead. If anything, all the fear being expressed every time Threads integration is brought up only emphasizes that this is not how it would play out
And that’s what I’m questioning. Would you? Would you think others here would? I wouldn’t. I’d rather go to whatever fork Fediverse devs favor instead. If anything, all the fear being expressed every time Threads integration is brought up only emphasizes that this is not how it would play out
The network effect can be strong. Say you’re now able to contact all your friends via your favourite Activitypub instance, you had to previously use Facebook.com or Threads or whatever but now they’re all here. You delete your Facebook and keep your Activitypub account to speak to all your friends who are on Threads.
Now Meta pulls the federation plug, or adds some feature that makes your Activitypub server not able to fully cooperate (Maybe you can talk, but you can’t video call anymore, or you can’t post GIF/images, whatever). Now what? All your friends are over there and getting annoyed with you. So… you eventually succumb and fire up a Threads account.
That’s no worse than you started. The fact remains nobody is going to get 100% coverage of their contact list on the fediverse without Meta, so trading a Facebook account for a threads account is no different, and it ignores the benefits of that time when you maybe able to live without either.
Right? I don’t know how to express any more clearly for the people who already are here that being here right now is the proof that there are people will choose a better platform over the most popular one. Unless they are admitting they are personally one temptation away from returning to Facebook.
I agree with you, I’m totally fine federating with them. If they choose to become incompatible with me, THEIR users will lose access to the content on the rest of the fediverse. They have an obligation to get ad revenue. If they can have someone else host the content, then use their interface to put ads and collect data on their users, it sounds like a win, as those users can still interact with me. If they really wanted to EEE and create incompatibilities, the rest of the ActivityPub instances just carry on as normal without supporting those extensions. The ecosystem already exists without the integration, so it’ll just go back to being separate again, exactly as it is now.
from https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html :
Basically keep people from using all the other platforms. Then stop supporting them. Similar like .docx never quite works in the open document editors. At least i refuse to believe that OSS devs are less skilled and motivated.
I’ve seen people bringing this up, but while they talk of EEE and XMPP, it seems like the analogy here is not being quite finished and formulated.
If we apply that to this, it seems like people are saying “if Meta changed the ActivityPub protocol to favor them and become incompatible with the rest of the Fediverse, Fediverse users would choose to return to Meta-owned platforms.”
And that’s what I’m questioning. Would you? Would you think others here would? I wouldn’t. I’d rather go to whatever fork Fediverse devs favor instead. If anything, all the fear being expressed every time Threads integration is brought up only emphasizes that this is not how it would play out
The network effect can be strong. Say you’re now able to contact all your friends via your favourite Activitypub instance, you had to previously use Facebook.com or Threads or whatever but now they’re all here. You delete your Facebook and keep your Activitypub account to speak to all your friends who are on Threads.
Now Meta pulls the federation plug, or adds some feature that makes your Activitypub server not able to fully cooperate (Maybe you can talk, but you can’t video call anymore, or you can’t post GIF/images, whatever). Now what? All your friends are over there and getting annoyed with you. So… you eventually succumb and fire up a Threads account.
That’s no worse than you started. The fact remains nobody is going to get 100% coverage of their contact list on the fediverse without Meta, so trading a Facebook account for a threads account is no different, and it ignores the benefits of that time when you maybe able to live without either.
Right? I don’t know how to express any more clearly for the people who already are here that being here right now is the proof that there are people will choose a better platform over the most popular one. Unless they are admitting they are personally one temptation away from returning to Facebook.
I agree with you, I’m totally fine federating with them. If they choose to become incompatible with me, THEIR users will lose access to the content on the rest of the fediverse. They have an obligation to get ad revenue. If they can have someone else host the content, then use their interface to put ads and collect data on their users, it sounds like a win, as those users can still interact with me. If they really wanted to EEE and create incompatibilities, the rest of the ActivityPub instances just carry on as normal without supporting those extensions. The ecosystem already exists without the integration, so it’ll just go back to being separate again, exactly as it is now.