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 sodiboo
Changes
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.Removed: > 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 delayed outrightAdded: > 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.
Show
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)
Original by sodiboo
Show
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 delayed 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)