592
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
592 points (96.1% liked)
Fediverse
28754 readers
519 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 2 years ago
MODERATORS
Ignore it. Defederate. Defederate with any instances that chose to federate with it. Keep the fediverse small and independent. It's nice here, let's keep it nice.
Yeap. It doesn’t to go mainstream; it’s already successful.
I keep asking but haven't gotten an answer, why must instances that block meta also block those that federate with META? Wouldn't blocking META be enough, as you wouldn't see their posta, nor users, nor comments in any way after blovking the domain?
Is this punitive or is yhere a reason I'm mising?
In a federated system, users on Alice can see and post into communities hosted on Bob, eg alice/c/funplace@bob. When Meta tries to join, Alice chooses not to federate - avoid giving meta free content, protect its users from 'bad' meta communities, preemptively block toxic meta users, whatever - but Bob does federate. Alice users can't see meta/c/advertising, there's no way to subscribe to Alice/c/advertising@meta. Both Alice and Meta users can see Bob/c/funplace, and so alice users can see anything that meta users post there and meta 'gets' any content that alice users contribute. Bob effectively acts like a tunnel between alice and meta users.
I got the impression that somehow your activity 3rd hand can still be passed on via the intermediary instance to Threads, and then becomes part of their dataset. I could be wrong, I'm not sure how that information gets passed on in the backend.
If you are worried about your data falling into the hands of Meta, don't worry, they already have it. Lemmy is incredibly easy to scrape by design.
What we should be more worried about is
This is the only way we can have a steady influx of new users.
Agreed, the data concern is a red herring. Might as well do a "I hereby revoke consent for Facebook to take my data..." post for all the good it will do you.
Block Threads because of the potential impact it can have on the quality of experience here. That's s good enough reason. Nobody joined a lemmy so that they could keep in touch with people who use social media to gossip about brands and influencers.