RexSystem3 votesoriginally by @fluxerhost on GitHub OP1 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.
RexSystem1 voteoriginally by @fluxerhost on GitHub OP
The good outweighs the bad here, because there is no "bad" for granularizing ACLs on existing actions.
I believe that this is a feature which should not be considered on its technical merits alone.
I, on the other hand, believe that this is a feature that can easily be considered on technical merits alone, because it is simply granularizing existing ACLs and actions.
It's true that there is probably not much obstructing the implementation, and that it could theoretically be useful to someone for a legitimate purpose. If you look at it like that, of course it'd be a good thing,
Well, that much is clear.
but technology does not exist in isolation of social realities, and it is easy to misuse it, accidentally or intentionally.
Misuse is the fault, concern, and problem of the misuser, not the developer, of a technology. Computers can be misused. Should we stop manufacturing computers? I'm not going to elevate this to a theoretical discussion, because that both misses the point of a technical feature request and is a waste of time.
I shall now show you how an existing feature can be "misused" by a "bad" administrator: channel visibility.
This is a feature that already exists in the Fluxer codebase, ACLs, etc.
I have seen this happen in a community already:
Users chat in #chat. They send messages.
Administrator creates #chat-2
Administrator removes channel read/visibility access for @everyone for #chat
Users' messages are now "locked away" in #chat, unable to be deleted, essentially immutable. The only way for a user to delete those messages is leaving the community and deleting all their messages, or, deleting their account and deleting all their messages, as I proposed above.
This is already possible with existing ACLs. The feature proposed in this discussion post does not introduce any new "risks" of any kind. Anyone can use or "misuse" any feature that already exists for any reason they desire.
It is up to users to participate in communities that they trust and are comfortable with the administration policies of.
Furthermore, "living messages" are a "misuse of necessity" of a chat platform. Just because all one has is a hammer, doesn't mean everything should be treated as a nail.
Will respond more tomorrow.
Thread
Comment by @fluxerhost
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 @fluxerhost
- Users chat in
- Administrator creates
- Administrator removes channel read/visibility access for
- Users' messages are now "locked away" in
This is already possible with existing ACLs. The feature proposed in this discussion post does not introduce any new "risks" of any kind. Anyone can use or "misuse" any feature that already exists for any reason they desire. It is up to users to participate in communities that they trust and are comfortable with the administration policies of. Furthermore, "living messages" are a "misuse of necessity" of a chat platform. Just because all one has is a hammer, doesn't mean everything should be treated as a nail. Will respond more tomorrow.#chat. They send messages.#chat-2@everyonefor#chat#chat, unable to be deleted, essentially immutable. The only way for a user to delete those messages is leaving the community and deleting all their messages, or, deleting their account and deleting all their messages, as I proposed above.