It is technically one-sided, and it works at the instance level, not the community level. If instance (server) A adds instance B to their defederated list: instance A ignores everything from instance B and does not send any updates to instance B. Instance B doesn't have to add instance A to it's defederation list, but it doesn't matter because it doesn't make a difference to what instance A is doing.
this post was submitted on 04 Jul 2023
2 points (100.0% liked)
AskBeehaw
2002 readers
2 users here now
An open-ended community for asking and answering various questions! Permissive of asks, AMAs, and OOTLs (out-of-the-loop) alike.
In the absence of flairs, questions requesting more thought-out answers can be marked by putting [SERIOUS] in the title.
Subcommunity of Chat
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 1 year ago
MODERATORS
I’d imagine you can’t allow a community to read only and not comment to another so that would necessitate defederation being bi-directional.
But would it be possible to have it read only? Or would that break functionality somehow (providing you at least inform the user they cannot comment or vote)?
It totally can. It's just not a feature at the moment. There's many federation restrictions that can exist but currently Lemmy only knows of like, ~3.
- Open to everyone and everything
- So everything is allowed, full-on communication
- Open to everyone and everything but with a blacklist
- So everything is allowed, full-on communication however blocklisted Community B becomes "dead" and can't interact with Community A.
- Allowlisted community
- You can only interact between allowlisted communties however when you go to Community B (allowlisted), you could see and interact with people from Community C (which is not allowlisted!) when in a Community of B but not of A. However, people from A cannot see or interact with communities of C and vice-versa.
view more: next ›