596
What should we do about Threads?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2023
596 points (96.1% liked)
Fediverse
28389 readers
252 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
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general 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), Search Lemmy
founded 1 year ago
MODERATORS
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.
Well the resistance isn't without reason:
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Agree, by design the fediverse should be able to resist whatever the supposed harm is from META, I don't really agree with privacy concerns since everything on the fediverse is public, especially on kbin and lemmy, almost everything is already available to whomever eants it, there is no need to set up this hugr machination since they can already accomplish it so much easier.
I'd like to add to this that there's no particular benefit to defederating preemptively instead of defederating in response to a problem.
Also, is this a problem we need to deal with? I think it matters for Mastodon instances, but I don't think Threads users will be interacting with Lemmy.