Asklemmy

43810 readers

1 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!

Open-ended question
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.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

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

founded 6 years ago

MODERATORS

170

What are some downsides of software being federated? (lemm.ee)

submitted 2 years ago by cybercitizen4@lemm.ee to c/asklemmy@lemmy.ml

100 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Eufalconimorph@discuss.tchncs.de 18 points 2 years ago

1: Anything that's federated is public (to instance admins) and can't be reliably deleted.

For ActivityPub, that's pretty much everything except user account.

For email (SMTP) that's sender, recipient, subject, and usually body.

Etc. Instance admins can log whatever they want. Laws like the GDPR or CCPA don't apply to all instances.

2: User signup is much harder because choice paralysis over which instance to join often sets in. That in turn leads to default recommendations, resulting in centralization in a few instances. E.g. lemmy.world, beehaw.org, sh.itjust.works, lemmy.ml for lemmy, Gmail, Apple mail, MS Live email, AWS email options for email.