Comment history
Versions of a comment on Separate out "edit own messages" and "delete own messages" permission in community permission settings, newest first.
Current version | Edited by astromahdi
Changes
It defeats the purpose of auditing if a non-audited fluxer instance “becomes” an audited instance (the non-audited history “taints” its absolute auditability)Removed: Maybe the option can be turned off if it had been enabled during setup — only one way.Added: 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.
Show
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.
Original by astromahdi
Show
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 — 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.