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@lemmy.world 18 points 9 months ago* (last edited 9 months ago) (7 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.

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.

[–] Kierunkowy74@kbin.social 8 points 9 months ago

I was looking for recommendations for alternative instances… I’d appreciate anyone actually responding to my comment.

OK.

Largest Lemmy instances blocking Instagram Threads are (according to fedipact.veganism.social) lemmy.ml, lemm.ee, lemmy.ca, Hexbear, feddit.de, Beehaw, Lemmygrad, lemmy.dbzer0.com, lemmy.blahaj.zone, discuss.tchncs.de, sopuli.xyz, aussie.zone, feddit.nl, lemmy.zip, midwest.social, feddit.uk, mander.xyz, ...

[–] Link@rentadrunk.org 7 points 9 months ago (2 children)

Can’t you block threads yourself once .world updates to 0.19.0?

[–] GONADS125@lemmy.world 6 points 9 months ago (1 children)

That's such a misinformative false 'solution' people keep peddling..

No, blocking Threads on the individual user level does not stop comments made by Threads users from showing up on federated instances, even for users who block Threads.

That means users who block Threads will still see hate/extremism and are still subject to potential harassment by toxic Threads users.

[–] Link@rentadrunk.org -1 points 9 months ago* (last edited 9 months ago)

I think there are many reasons to block threads but is toxic users one of them?

There are lots of toxic users on Lemmy too. Should we be blocking lemmy.world or lemmy.ml because they have a few toxic users too?

[–] dameoutlaw@lemmy.ml 3 points 9 months ago (1 children)

In a Mastodon level this is not true. Blocking Threads.net prevents you from sharing your content with them and for their content to show up. Pixelfed has also enabled user level Authorised fetch which will prevent Threads.net from attempting to fetch that users content

[–] GONADS125@lemmy.world 2 points 9 months ago

That's good to know. Thanks.

[–] TORFdot0@lemmy.world 3 points 9 months ago

Just because Lemmy.world doesn’t agree with about defederating with meta doesn’t make them sell outs. Like you said, you are jumping ship; just like the fediverse intended.

For better or worse, Lemmy.world is intended to be a catch all instance for normies so it makes sense why they would not defederate from meta.

[–] Valmond@lemmy.mindoki.com 2 points 9 months ago (1 children)

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

[–] GONADS125@lemmy.world 3 points 9 months ago

I created !vans@lemmy.world 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.

[–] ShadowRam@kbin.social 1 points 9 months ago (1 children)

I don't get, even if you are part of .world and they are federated with threads.

Can't you just personally block all threads?

You personally can defederate without it affecting anyone else.

[–] GONADS125@lemmy.world 6 points 9 months ago

No, that's a half-measure at best... It only blocks Threads posts from showing up in your feed. It does not block Threads users comments from showing up on federated instances, even if the individual user personally blocks them.

I am legitimately fearful for LGBTQ+ users, as their community members have already been harrased on Threads by the far-right.

[–] rglullis@communick.news 1 points 9 months ago

Nothing ever stopped you from creating you own instance. With blackjack and beers.