this post was submitted on 07 Jul 2023
93 points (91.2% liked)

Asklemmy

43945 readers
499 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

I saw in the posts recently how Metas thread grew rapidly in a span of just a day. I understand that since threads posts a privacy nightmare (no surprises there) Iโ€™m leaning towards de-federating with them.

But I am also cautiously excited about the massive amount of content if we federated instead.

So for purposes of discussion, may I know the pros and cons of federating with threads?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] dandroid@dandroid.app 2 points 1 year ago

Data security. it's Meta. Any and all user information, including admin data, naturally exposed by federated services instantly gets sucked into the Zuck data vacuum to build a user profile. Right now, we're still reasonably insulated from them.

Couldn't they just run another instance and not tell us the domain name and silently steal all our data anyway? I feel like there is no way to have data security when it is decentralized. All my Lemmy data is on hundreds of other servers already.