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
[-] Roundcat@kbin.social 30 points 1 year ago

It's not much of privacy I'm concerned about as much as community and visibility.

Meta is infamous for fostering insufferable users, meanwhile from what I have seen from kbin and lemmy, there is a lot more nuance and maturity in the communities here (for the most part) that I would hate to see overun by Thread users.

Secondly, it's one thing to be visible to the internet in general, but to have anything tied to Meta that they can scrape and sell is a concern to me. The fact that the fediverse is a prototype with vulnerabilities makes the likelihood of a company like Meta, who intentionally exploits vulnerabilities to harvest data, all the more likely.

Finally, almost every example of a large company joining a federation always ends with said company cannibalizing the federated networks, and I have no reason to believe Facebook won't do this. If I'm going to invest time and effort into making a community grow, I would rather not waste my time on a platform that is doomed to be consumed.

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

So. In 1 day, Threads has gotten more users than all of Mastodon combined. My friends are on Threads. They're not coming to Mastodon. I've tried. I couldn't even convince my fiance to join me on Mastodon for longer than a day, and we live together.

How would you suppose I talk to my friends? By joining Meta? Or by staying with FOSS on the fediverse? Because when you say "everywhere needs to defederate from Meta" you're also saying "You shouldn't talk to your friends here, nor should your friends be able to talk to you."

Quite frankly - I really enjoy that I can both be here and still be in contact with my friends. Meta can't track me here (as much, I'm aware they can still siphon data but they could do that regardless). I'd much rather stay here if I can. But if given the chance to choose, I'm going to move to somewhere that federates with Threads. Not because I like Meta - I hate Zuck almost as much as I do Elon, which is quite a lot - but because I'd rather see and talk to my friends than be locked in with a bunch of rando control freaks jumping at shadows.

If the fedipact had it their way, anywhere that federated with Threads would in turn become defederated. This will create 2 separate fediverses. People will have to choose which one they spend time on - even if they have accounts on both sides, one will always be the "primary" account.

I posit that for many people, the "primary" account is going to be the one with their friends and interests. It's going to be the side with the influencers they follow. Simply, it's going to be the one that federates with Threads. The other side will slowly wither and die, as all the content dries up and people move to where the network effect is strongest.

You can argue that we need to defederate because of "embrace, extend, extinguish". Tell me: what is the end result of EEE? A diminished fediverse, where most people use the single app that has all the people and all the content. How is that different than the splintered fediverse caused by the fedipact?

It's really not much different at all. If Meta goes for EEE, there is no stopping them. If the fedipact takes hold and rabidly defederated anywhere that glances at Meta, then the fediverse's network effect will shatter. The fedipact will simply backfire and shoot themselves in the foot as people choose the side with the larger network effect. It's ridiculous that the idea has gotten as much traction as it has; the fedipact's best-case scenario is worse than the worst-case of EEE.

If a bunch of people want to live in small segmented communities, that's on them. Beehaw is right there if you want it; that's what Beehaw aspires for. But large, general-purpose instances shouldn't bow to the whims of a loud minority that don't even realize the repercussions of their agitations.

The fediverse is at its strongest when we federate. That's what makes this place special. We've agreed that walled gardens are bad, and the one time that we have a chance to get a bunch of "normal" users on the fediverse everyone panics because they're afraid of EEE.

The fedipact isn't going to stop EEE. If Meta wants to do EEE, they're going to do it with or without the fedipact. We don't even know for sure that EEE will happen - it's true that Meta is a business, but there are plenty of open protocols you use every day that never got hit by EEE. L

All the fedipact will do is hurt people who want to use free software to see their friends so this loud minority can exercise their control over everyone.

You have the power to block the domain here if that's what you want to do. Please don't let your personal fears ruin the experience of others.

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

I'm okay with a small bubble of randos as my Fediverse, I don't need -- or want -- my social media to be "everybody".

I'm in a discord with my friends and that's pretty much all I need.

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

That's fair, but I personally want my social media to be "everybody".

That's actually what brought me here to Kbin - I loved that it had Mastodon integration and connected everybody to everybody else.

I was originally on Beehaw, which is very much trying to capture that "Discord with my friends" feel. And that's totally fine; I understand that and respect it and think it's valid.

But the point is that we have options. Kbin especially is great because these options can happen at a user level; you can go in and block entire instances from your user account, and it'll be just as if that instance was defederated. Admins don't need to maintain a short allowlist or a large denylist; you can curate it to your comfort level on your own.

But I'll also recognize that it's not inherently a small community - you're taking a big community and slicing off parts of it, which isn't the same. But there are spots for that cozy feeling across the fediverse if that's what you want. I just don't think a broad flagship instance like Kbin.social should be one of those spots.

load more comments (24 replies)
load more comments (69 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