this post was submitted on 06 Jul 2023
593 points (96.1% liked)

Fediverse

35392 readers
109 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 !moderators@lemmy.world!

Rules

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

founded 2 years ago
MODERATORS
 

A lot of people dislike it for the privacy nightmare that it is and feel the threat of an EEE attack. This will also probably not be the last time that a big corporation will insert itself in the Fediverse.

However, people also say that it will help get ActivityPub and the Fediverse go more mainstream and say that corporations don't have that much influence on the Fediverse since people are in control of their own servers.

What a lot of posts have in common is that they want some kind of action to be taken, whether it'd be mass defederating from Threads, or accept them in some way that does not harm the Fediverse as much.

What actions can we take to deal with Threads?

(page 2) 50 comments
sorted by: hot top controversial new old
[–] notatoad@lemmy.world 16 points 2 years ago (3 children)

we shouldn't do anything.

Isn't the whole promise of the fediverse that whatever the policies of one instance are, that doesn't necessarily affect all the other instances, and each can do their own thing. If an instance doesn't want to accept traffic from threads, good for them. But to try to organize a fediverse-wide response to threads seems a whole lot like the centralization the fediverse is supposed to not be.

load more comments (3 replies)
[–] Ipodjockey@lemmy.world 16 points 2 years ago

Fuck em. Burn this place to the ground before we dance with the devil.

[–] bizzle@lemmy.moorefam.net 16 points 2 years ago

I have already blocked threads on my household instance. I decided that I don't want to have to trust major instance admins to take the same things seriously that I do.

[–] Macallan@lemmy.world 15 points 2 years ago

Another vote to defederate here.

[–] Empyreus@lemmy.world 14 points 2 years ago (1 children)

Threads is exactly showing the biggest problem with anything Fediverse. It's simpler for the user so it will be accepted. The amount of people I've already seen join is huge compared to mastodon.

[–] marigo@lemmy.world 13 points 2 years ago (1 children)

Lemmy doesn't need to be #1 in popularity. I'd prefer it to split and maintain a higher level of quality, even if it's smaller as a result. Even if Meta can grab data either way, it should be disconnected on principle.

load more comments (1 replies)
[–] guy@lemmy.world 13 points 2 years ago (1 children)

Given that everything right now is just speculation - I say sit tight, observe what actually happens and respond appropriately if it does start to go wrong. Defederation is very easy, we can do it when we need to

load more comments (1 replies)
[–] irkli@lemmy.world 12 points 2 years ago* (last edited 2 years ago) (1 children)
[–] emperorbenguin@lemmy.world 8 points 2 years ago

What an excellent article. Informative and to the point.

Recommend everyone read it.

[–] JoYo@lemmy.ml 10 points 2 years ago

threads will never federate.

[–] Zoldyck@lemmy.world 7 points 2 years ago (7 children)

I think defederation isn't the solution. Am I dumb in thinking this could actual have a mutual benefit?

Just an example: I will never use Threads, but if I can communicate with them from my Mastodon account, I would like to have that option.

load more comments (7 replies)
[–] Z4rK@lemmy.world 7 points 2 years ago (2 children)

What’s the DNS I need to block to never inadvertently get sent to anything Threads related?

load more comments (2 replies)
[–] AnUnusualRelic@lemmy.world 6 points 2 years ago

Same thing we do about reddit. They are free to do their own thing in their own corner as long as they don't bring us into it.

load more comments
view more: ‹ prev next ›