this post was submitted on 21 Dec 2023
309 points (96.1% liked)

Fediverse

28691 readers
849 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago
MODERATORS
309
submitted 1 year ago* (last edited 1 year ago) by chitak166 to c/fediverse
 

I used to think that there would be 1, main 'Fediverse' with all of the 'big instances' connected to each other. The recent Threads debacle has shown me otherwise.

The point of the Fediverse is that there is no one single entity, or group of entities, dominating it all.

Right now it feels like whatever the big instances do, we kind of have to go along with to be a part of anything. As the Fediverse grows, there will be more options to suit different types of users.

I think it's fine if big instances federate with Threads and it's fine if they don't. People can just join instances that align with what they want. It's not like defederating means being cut out of the Fediverse, that's not possible.

Great design. I'm eager to see how it plays out.

you are viewing a single comment's thread
view the rest of the comments
[–] GONADS125 11 points 1 year ago* (last edited 1 year ago) (37 children)

Edit: Since so many people are misinformed: No, blocking Threads on an individual basis is not a solution. This only blocks posts from Threads showing up in your feed. It does not block Threads users' comments from spreading hate and extremism throughout federated instances, and lemmy users will still be subject to potential harassment from Threads users. (See the harassment of the LGBTQ+ community on Threads for examples...)

Here's a comment of mine that states my argument against federating with Threads.

Also, I was not trying to debate the issue here. I was looking for recommendations for alternative instances... I'd appreciate anyone actually responding to my comment.

Original comment: Anybody have recommendations on a decent instance that won't be federating with Threads? Maybe one that allows community creation but isn't full of tankies?

I'm jumping ship from .world if they go through with federating with Threads. Such a shame to see the effort put into building this great instance come undone.

This place decided to disregard what the majority of their users want and turn the neighborhood to shit way faster than reddit. I thought we'd at least have a couple years before instance admins started selling out to such a shitty company that's going to make the fediverse a less safe place for their users.

Meta will also do anything they can to EEE and I'm not convinced the fediverse is as invulnerable to such exploitation as some users seem to be.

[–] [email protected] 3 points 1 year ago (1 children)

Would you create a community, and if so, what kind?

[–] GONADS125 5 points 1 year ago

I created [email protected] and have been planning on trying to revive my efforts to grow the community, but I'm sure hell not doing that if Threads is being incorporated. I'm instead going to strip the community of all of the content I posted.

I also want to create a community for my city, but I'm never going to do that on an instance that allows Threads/Meta incorporation. Also have wanted to recreate r/OldSkaters from reddit.

If I wanted to deal with Meta, I'd make an account on one of their privacy/rights-infringing platforms.

As established already, blocking Threads does not block user comments from showing up. Even if it did, I still would not host a community on an instance federated with Threads unless there was a way for the communities themselves to fully block Threads interaction.

But the only way to fully block Threads is by defederating from it.

load more comments (35 replies)