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

(#3454) Feature Open: Under consideration community moderation

Thread

Comment by @fluxerhost
RexSystem 3 votes originally by @fluxerhost on GitHub OP 3 replies

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 2 votes originally by @Shardion on GitHub 2 replies
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.
Comment by sodiboo
sodiboo 2 votes edited 1 reply
I think the idea of having a distinct "Business Fluxer" for legal compliance makes sense. It wouldn't really need (at least, technically) to be a separate fork if we just want this one feature. It could be an instance-wide toggle at setup.
Should this instance be immutable for legal compliance reasons? Federation will be disabled, deletion of messages will be disabled (instead, perhaps, they can be "hidden"), edit histories will always be visible to everyone, and channels and guilds can only be archived; not deleted outright
^ or this could be only settable with an environment variable, to prevent encouraging non-bureaucratic users from using it for evil reasons (i'm generally of the opinion that this feature is overall harmful, but i also recognize that it may be Legally Required in certain cases), and also just to prevent asking confusing questions with major irreversible implications to users who don't need it. But it's worth considering if any current Fluxer users even need this feature? Surely none of the commenters here are considering hosting it for business or government use. And, i believe those use cases need specific certification or audits? Even if Fluxer builds the perfect software for them, it doesn't mean Fluxer can be used for them automatically. so, the "Business Fluxer" fork would be the most suitable way forward here, in my opinion. Not for technical reasons (the feature would not be infeasible to implement in upstream), but purely for the compliance reasons of How Such A Product Must Be Developed In The First Place. let someone else handle the compliance side of things. Fluxer HQ can focus on building a chat platform for normal people. or, at least, wait until a business user comes along and wants to help develop the feature for upstream fluxer (in a way that is actually compliant with their policies)
Comment by astromahdi
I think an instance-wide configuration option only on initial setup makes sense. It defeats the purpose of auditing if a non-audited fluxer instance “becomes” an audited instance (the non-audited history “taints” its absolute auditability) Maybe the option can be turned off if it had been enabled during setup -- essentially, a feature that "goes" only one way. I am aware of a user who wants to host a fluxer instance for business use, and is willing to fund/support the development needed for the usecase.