Separate out "edit own messages" and "delete own messages" permission in community permission settings

(#3454) Feature Under consideration community moderation

Thread

Comment by @fluxerhost
RexSystem 1 vote originally by @fluxerhost on GitHub OP 1 reply

Example use case for this feature: running fluxer in a corporate setting, or for a law firm.

"Legal discovery" and evidence preservation for all messages must be preserved. If an employee leaves or is fired, they don't get to take their messages with them. If an employee is involved in a corporate investigation (e.g. harassment), the investigations team should be able to extract all messages sent by the user. Message immutability via expanded ACLs is a good first step to support such safety. It is more technically complex, but also a good idea, to preserve all edit and delete history, however it is also a good feature and easy to implement to add message immutability/making the ACLs around messages more granular.
Comment by @Shardion
RexSystem 1 vote originally by @Shardion on GitHub
There is nothing that can enforce an instance to only be able to federate with other instances running the same code, and it doesn't happen automatically, even when incompatible changes are introduced. This is actually why I suggested a fork! If such a fork existed, say, "Business Fluxer", and was made intentionally incompatible, maybe by ripping out the federation code entirely, then the legal use-case could have its own Fluxer, without the data privacy features for compliance reasons, and personal users on the federated network get to keep their data privacy in the safest way possible.