110

I would like to know if I can feel safe here, or if I should pack it up and start looking elsewhere sooner rather than later.

If the kbin staff have already made there intentions clear, please let me know.

you are viewing a single comment's thread
view the rest of the comments
[-] duringoverflow@kbin.social 9 points 1 year ago

what you (and other likeminded people) haven't understood is that these 2 are 2 different topics. Defederating with meta is not because people don't want to be near the users of meta. It is because meta is a huge corp and it is not here to promote the idea of a federated network. It is here to make profit and to exploit the network. Allowing them to be part of the same network will just cause harm to the network itself in the end.

I suggest you reading this article https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html which is the story of how google killed XMPP, written by one of the XMPP core developers. I believe you will see the similarities.

@asjmcguire

[-] EnglishMobster@kbin.social 4 points 1 year ago

I think misunderstand. I do understand that. I used XMPP. I've read that article.

My argument is that the fedipact, if executed as desired by the people running it, will defederate from Meta and anywhere that federates with Meta.

So now you have 2 fediverses, completely separated from one another. One side has Meta; the other doesn't. If I want to post something and I want people to see it and react to it, I will post it to the side with more people. If I want to scroll endlessly without needing to stop and refresh or wait because the feed is stale, I will look at the side with more people.

The other side - the fedipact side - will slowly become stale and niche. There will always be hardcore users - people still use XMPP - but it will fade into what it was in 2020 and 2021. My Lemmy account - @EnglishMobster - is from 2020. My original Mastodon account is even older. I've seen this place grow and blossom into what it is now, and the fedipact is threatening that growth. People will leave the side of the fedipact and join the side without it... which is to say, the side dominated by Meta.

Instead of a big wide fediverse with open source projects living alongside random PeerTube creators living alongside movie stars... we have 1 niche one and 1 dominated by a large corporation. It's literally the same result as if Meta went through with Embrace, Extend, Extinguish... but done without the "extend" or "extinguish", a massive "own goal" by the FOSS community.

And worse - it doesn't stop Facebook from going through with "extend" or "extinguish" later. It literally just destroys communities for no reason, leaving us in the exact same situation that XMPP is in today.

I am fine with an instance saying "we won't federate with Threads". I'd rather it not be Kbin, of course, but I will move to an instance that does federate because my friends are important to me.

I am not fine with me being held hostage for that. I don't want to join Threads directly if I can avoid it; I'd rather use my Kbin account. But the fedipact is trying to make that impossible by saying "we will defederate anywhere that federates with Threads".

[-] livus@kbin.social 6 points 1 year ago* (last edited 1 year ago)

If I want to post something and I want people to see it and react to it, I will post it to the side with more people

If that's the case, presumably you're in the fediverse for other reasons? If audience size is central to you, wouldn't you be on reddit and insta/facebook?

[-] EnglishMobster@kbin.social 1 points 1 year ago

To an extent, but morality is important to me too.

I don't use Facebook because they corrupt democracy. I don't use Twitter because Elon Musk is a wannabe fascist. I don't use Reddit because they have refused to clamp down on bad actors and have directly insulted their users.

If everyone defederates from Threads, I won't use Threads, because I don't use Facebook. My morals are more important to me than audience size.

But... as things stand, once Threads federates with the wider world, I will be able to interact with my friends without letting Zuck near me. In a most ideal world, they'd be able to follow me here on Kbin and I can follow them back. I'd see their posts in the Microblog feed and sorted into magazines, and I can like and comment and boost without logging into Zuck's website and letting him have my data again.

You can say that's supporting Facebook. Maybe. But if Threads is truly federated, then Facebook would basically be able to go anywhere regardless; in that sense I'd be supporting Threads whether I was talking to someone directly or not.

And in that sense, I totally see why people say "we shouldn't federate with Meta, they're evil and they're selfish and they're going to destroy the fediverse." I can understand why people personally would want to choose somewhere that doesn't do that. I don't think this instance should block Meta because it's large and general-purpose, but somewhere like Beehaw where that sort of thing is part of the mission statement... I get it.

But from my perspective, I am given the chance to talk to a large group of people; people who share the same interests as me; people I know in real life. People who would see my stuff - but (more importantly) I'd also see theirs. And I'm sure most people feel the same way; they're going to where the people are. This'll naturally create an audience, one that gives a wide variety of fresh content and also responds to content you give.

I'd much rather have that then return to 2020-era Mastodon where you'd be lucky to get 3 interactions to a Toot, and you'd see everything there is to see in 15 minutes (at most).

[-] livus@kbin.social 2 points 1 year ago

I think I might have misunderstood your wider point. The part where you were positing a hypothetical in which the fediverse splits and one side has Meta. I thought you were saying you will align with the Meta side because of audience size.

Which kind of implies that if Meta then moves into the Extend Extinguish phases you would end up at Threads?

[-] EnglishMobster@kbin.social 2 points 1 year ago* (last edited 1 year ago)

At the Extend phase I would encourage fighting back - or at least making it clear that we are separate from Threads and shouldn't copy them.

I wouldn't leave for Threads during Extinguish; I'd stay here. But I would just sit back and mourn what could've been.

Just like how I mourn XMPP whenever I see Pidgin in software center.

Just like how I mourn when my Windows Phone had SMS, Hangouts, and Facebook Messenger all in the stock texting app.

I'll survive. I'm not going to Zuck's site. But I'll be really sad that I'm not going to be able to talk to my friends from anywhere else.

load more comments (1 replies)
load more comments (23 replies)
load more comments (23 replies)
this post was submitted on 06 Jul 2023
110 points (100.0% liked)

/kbin meta

2 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago