Edit history

Separate out "edit own messages" and "delete own messages" permission in community permission settings has not been edited, so there are no earlier versions.

Current version | Original by Rex
Show

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

Current problem

Currently, the send messages permission covers send, edit, and delete, of messages sent in a channel.

Proposed change

Splitting out the "edit" and "delete" messages permissions as options in the Role settings in a community. This allows channels to be one-way write, so that things such as "edit trolling", sneaky behavior, or otherwise disruptive activities can be limited in either channels, categories, or an entire community. The clear technical reason for this is making existing ACLs as granular as possible on a technical level.

Additional information

The core motivation behind this is: there should be as granular controls as possible for features in community admin/owners' hands. Splitting out the "send/edit/delete message" ACL is a valid technical decision and a good one. This is also important for channels, categories, or communities where it is important that people "stand behind what they say". Maybe a one-time notice should be shown to the user when entering such a channel with such settings -- "note: you can not edit" or "note: you can not delete messages in this channel" -- similar to the "note: nsfw content" dialog that appears before opening an nsfw channel for the first time? additionally, could it be possible to have an "edit" and "delete" timer setting -- so that in case an admin wants a channel to have "5 minutes of edit permission" or "5 minutes of delete permission", it's possible? as in, a time after sending a message, that messages can be edited or deleted? from seconds to minutes to hours to days. One example is to again prevent edit trolling.

Details

Fluxer.com (the instance) , for example, would NOT need to enable this feature on its own instance if it does not desire, but it should be part of the codebase for other self-hosted instances to enable. There are many features that are possible on self-hosted instances, but not on the main Fluxer.com instance, for example. This is no different.

This is also useful for e.g. giveaway channels where users enter their 'ticket' in for a giveaway (e.g. answer to a problem, guess, etc) and shouldn't be able to edit their message after sending.