Federation explicit denylist and allowlist support #31

Closed
opened 2023-12-23 19:45:53 +00:00 by girlbossceo · 1 comment
girlbossceo commented 2023-12-23 19:45:53 +00:00 (Migrated from github.com)

Similar to Synapse's options: config options and/or admin room commands to support denying federation with certain servers, and allowlist servers for an allowlist-only federation setup.

Similar to Synapse's options: config options and/or admin room commands to support denying federation with certain servers, and allowlist servers for an allowlist-only federation setup.
girlbossceo commented 2024-03-31 04:48:03 +00:00 (Migrated from github.com)

Rethinking this now, I don't think this feature is particularly useful in practice. Malicious/offensive events will just be federated to you through other servers in the room.

It's only somewhat useful for blocking DMs / room invites from a server, and even then it needs to be extended to client /sync not just on the receiving federation endpoints.

Additionally, a private federation setup should be done with a firewall and not purely on the application level.

Conduwuit has implemented a lot of moderation utilities since this was made. If a better use-case for this comes up that existing tools cannot cover, we can look at this again. The work in the submitted PR may be repurposed or referenced for some other future things.

Rethinking this now, I don't think this feature is particularly useful in practice. Malicious/offensive events will just be federated to you through other servers in the room. It's only *somewhat* useful for blocking DMs / room invites from a server, and even then it needs to be extended to client `/sync` not just on the receiving federation endpoints. Additionally, a private federation setup should be done with a firewall and not purely on the application level. Conduwuit has implemented a lot of moderation utilities since this was made. If a better use-case for this comes up that existing tools cannot cover, we can look at this again. The work in the submitted PR may be repurposed or referenced for some other future things.
nex added the
Inherited
label 2025-04-14 23:38:30 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: continuwuation/continuwuity#31
No description provided.