this post was submitted on 06 Jul 2023
9 points (100.0% liked)

Fediverse

287 readers
1 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago
 

Something I don't understand currently about the whole Meta/Threads debacle is why I'm seeing talk about instances which choose to federate with Threads themselves being defederated. I have an account on mastodon.social, one of the instances which has not signed the fedipact, and I've had people from other instances warn me that their instances are going to defederate mastodon.social when Threads arrives.

I have no reason to doubt that, so, assuming that they are, why? I don't believe instances behave as any kind of relay system: anybody who wishes to defederate from Threads can do so and their instances will not pull in Threads content, even if they remain federated to another instance which does.

I'm unsure how boosts work in this scenario, perhaps those instances are concerned that they'll see Threads content when mastodon.social or other Threads-federated instances users boost it, or that their content will be boosted to Threads users? The two degrees of separation would presumably prevent that, so I can see that being a reason to double-defederate, assuming that is how boosts work (is it?).

Other than that, perhaps the goal is simply to split the fediverse into essentially two sides, the Threads side and the non-Threads side, in order to insulate the non-Threads side from any embrace, extend, extinguish behavior on Meta's part?

Ultimately, my long term goal is just to use kbin to interact with the blogging side of the fediverse, but there are obviously teething issues currently, like some Mastodon instances simply aren't compatible with kbin. I'm too lazy to move somewhere else only to move to kbin "again" after that, so in the short term I guess I'll just shrug in the general direction of Mastodon.

To be clear, I have a pretty solid understanding of why people want to defederate Threads (and I personally agree that it's a good idea), it's the double-defederation I'm not sure I follow. Is my understanding at all close? Are there other reasons? Thanks for any insight.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (3 children)

I'm aware of the history - I used XMPP myself, for a long long time. I'm mad it's effectively gone.

Heck, on my Windows Phone once upon a time I could have chats with SMS, Facebook Messenger, and Google Hangouts all without leaving the stock native texting app. One by one they all broke and faded away.

But my point is - is the fedipact a better outcome?

My thought is no, it isn't. The intention of the fedipact is to split the fediverse in two - the side that federates with corporations, and the side that doesn't.

But the issue is that in splitting the fediverse when it's still so young and fragile, you're going to inherently kill it. Even if people maintain accounts on both sides of the divide, time is finite. People will make a choice to participate in one side of the fediverse or the other, knowingly or not.

My gut tells me people are going to want to go where the network effect is strongest. They're going to go where they know the people, where Wil Wheaton or Arnold Schwarzenegger might randomly pop up in the replies to a post.

And this is going to cause people to choose the side of the fediverse that gives them that interaction. Some may still choose to stay true to the fedipact - just as people do still use XMPP and IRC - but if the fedipact goes as intended, the fediverse will splinter and most people will go to the side with their friends.

I don't see how that world where the fedipact is successful is any different than the option 2 you laid out. The fedipact has caused 2 fediverses: one that has lost the network effect and is beginning to decay; the other dominated by a corporation. The fedipact side will have few people left because everyone left to talk to their friends on Meta.

The only way forward is to hope for option 1. Is it foolish? Maybe. Meta is a corporation that wants money. XMPP died a bad death. You can even argue that email is dead as an open protocol now - ever try sending an email message on your own server?

But we can hope for a situation like what we're seeing with ZigBee/Matter where an open, clear standard is maintained. And maybe that'll change in a decade, but the only thing the fedipact does is remove any hope for that at all.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

Please Zuckerberg, save the fediverse!

[–] [email protected] 3 points 1 year ago

What frustrates me is that it makes total sense for people who want their own corner of the fediverse to defederate liberally and keep their community small. Not every instance is trying to be Reddit; some are basically a special-interests messageboard.

But the fedipact is not a group of people building their own more private network, it's just culture war and bullying. Instead of being a positive, it's all negative.

[–] [email protected] 2 points 1 year ago

I agree. I think people who support the fedipact greatly underestimate the network effect. To be honest, I think this place is never going to get big--it has the same issues that Linux desktop has. It'll only ever be used by a small niche group. I still have some hope but it's quickly draining.