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 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.