Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't allow moderators to edit anyones messages #9793

Closed
nadonomy opened this issue May 21, 2019 · 17 comments
Closed

Don't allow moderators to edit anyones messages #9793

nadonomy opened this issue May 21, 2019 · 17 comments

Comments

@nadonomy
Copy link
Contributor

nadonomy commented May 21, 2019

We've discussed making it possible for moderators to edit anyones message in future. Although the plan would be to expose mod edits in both the (edited) label and the 'View Edits' modal, there's something that fundamentally rubs me the wrong way about the platform letting some users put other words into other users mouths.

The established precedent for this is traditional forum software. However, we should consider taking inspiration from more modern discussion platforms like Reddit where moderators can mute/redact comments, but not edit them.

It's important that the matrix spec/protocol is able to support mods being able to edit messages, however we can choose not to expose this in Riot.

If we decide for this, we should also consider filing an issue or expanding #9792 to include notifications for being moderated.

After figuring out how to move forward, we should track the conclusions in riot-meta to then feed work into all platforms.

@bwindels
Copy link
Contributor

Presently, it's possible for moderators to edit anyones message.

This should not be possible at the moment. Where are you seeing this?

@bwindels bwindels added the X-Needs-Info This issue is blocked awaiting information from the reporter label May 22, 2019
@nadonomy
Copy link
Contributor Author

Presently, it's possible for moderators to edit anyones message.

This should not be possible at the moment. Where are you seeing this?

Ah thanks. Edited the parent issue comment to better reflect the current functionality. Will leave this issue open for discussion when we visit this in future.

@bwindels bwindels removed the X-Needs-Info This issue is blocked awaiting information from the reporter label May 28, 2019
@anoadragon453
Copy link
Member

I would like to keep the functionality for bot-related reasons, but am fine with the functionality not being exposed in Riot.

@babolivier
Copy link
Contributor

babolivier commented Jun 19, 2019

NV hat off

I kinda feel like it might not be something good to keep in Matrix in the long term to allow people to edit other people's messages without their content. It feels really close to impersonation to me. The main argument I'd see would be moderation when a message is breaking a room's rules, and redaction is more than enough for that.

I would like to keep the functionality for bot-related reasons

I'd be fine with a bot editing messages on my behalf only if I give it access to my account, otherwise it sounds incredibly intrusive to me.

It's important that the matrix spec/protocol is able to support mods being able to edit messages

I must admit I'm failing to see how it's something desirable, could you please elaborate?

@anoadragon453
Copy link
Member

It's important that the matrix spec/protocol is able to support mods being able to edit messages

I can think of many examples of bots that would be handy. A bot that translates people's messages from one language to another. A bot that removes tracking data from URLs that are posted to a channel. A bot that removes annoying emoji from people's messages.

In addition having multiple accounts with the ability to edit the same content can be wildly useful for all sorts of things inside and outside of chat.

If an admin/mod controls the room, they should be able to manipulate content in it.

Of course we need to be clear about how the message arrived in that state. We need to a) allow people to view message history, and b) be clear without requiring anything more than a glance as to who edited the message last.

@ara4n
Copy link
Member

ara4n commented Jun 20, 2019

From my perspective, we want to support this in the protocol, so long as the edit history is maintained (assuming the edits are not redacted) and the fact that the msg was edited by a given user is made abundantly clear in the UI. The reasons are:

  • The use case of bridging platforms such as messageboards where it's common for mods to edits msgs (e.g. to add spoiler tags, or to split off offtopic content)
  • Mods can redact messages anyway, which is almost more unpleasant than editing them (especially as it by definition doesn't leave the history behind)
  • Having a mod able to go in and edit out sensitive content (e.g. delete an access_token from someone's message, or add a spoiler tag, or even fix a markup problem) doesn't seem unreasonable.

@babolivier
Copy link
Contributor

babolivier commented Jun 20, 2019

NV hat still off

From my perspective, we want to support this in the protocol, so long as the edit history is maintained (assuming the edits are not redacted) and the fact that the msg was edited by a given user is made abundantly clear in the UI. The reasons are:

  • The use case of bridging platforms such as message boards where it's common for mods to edits msgs (e.g. to add spoiler tags, or to split off offtopic content)

  • Mods can redact messages anyway, which is almost more unpleasant than editing them (especially as it by definition doesn't leave the history behind)

  • Having a mod able to go in and edit out sensitive content (e.g. delete an access_token from someone's message, or add a spoiler tag, or even fix a markup problem) doesn't seem unreasonable.

Right, I see your point, and I agree that it has some benefits. Though I just can help but think of the potential for abuse and how it has a non-zero probability to cause some mess at some point.

To me, the UI/UX for something like that is hard to get to a point where the information of which part of the message has been written by whom is as clear and obvious to everyone as the fact that the message has been edited (more than just providing edits history, because I don't believe edits histories are read by the majority of users), and every client must get it right here, and the whole thing sounds super complicated and not so realistic to me.

I kinda fear that this might make people afraid to interact in somewhat crowded rooms because it may mean that some mod they don't know can impersonate them to (at least) part of the members in the room (because it would make me so). Matrix is particularly attractive to people who want full control over their data and this sounds like a step in the opposite direction to me.

Mods can redact messages anyway, which is almost more unpleasant than editing them

tbh I'm way more comfortable with someone deleting a message than sticking a statement I have never said or thought under my name.

be clear without requiring anything more than a glance as to who edited the message last.

To me we need that level of clarity for who edited which part of the message last. If X and Y both edit the same message, you need to be able to clearly identify who wrote what as easily as identifying who sent which message imho.

@ara4n
Copy link
Member

ara4n commented Jun 20, 2019

I see the concern, but surely sticking "Edited by Matthew" at the end of the message (similar to how we have just "Edited" today) is going to stick out like a sore thumb?

@turt2live
Copy link
Member

(it sticks out pretty obviously on github, which is good)

@ara4n
Copy link
Member

ara4n commented Jun 20, 2019

the fact that github lets mods edit msgs is another example of why you need matrix as a protocol to support the concept, otherwise the impedance mismatch of bridging such threads into matrix is going to be an arbitrary and avoidable pain in the ass.

@Half-Shot
Copy link
Member

Half-Shot commented Jun 20, 2019

A benefit I think nobody has brought up yet is that you can see toxic moderators in action if malicious edits have the editors name visible. It might actually be useful in red flagging folks that could tie into reputation work later.

Edit: and obviously not show third party edits for people who have low reputations?

@equinox
Copy link

equinox commented Jun 20, 2019

@babolivier has summarised most of my concerns regarding this, and I think that explicitly giving consent for someone to edit your messages is the best compromise.

If a moderator takes issue with a message you've sent, they already have the options of redacting it or replying to it (which gives people the context of the message), so in essence there's no missing contextual problems to confuse people as to what the moderator is replying to. Which would have maybe been a pro for the ability to allow moderators to edit messages if replies weren't a thing.

@babolivier
Copy link
Contributor

babolivier commented Jun 20, 2019

NV hat still off

(it sticks out pretty obviously on github, which is good)

I'd say GH's UX is good enough for tech people (or at least people used to VCSs and going through histories), which I assume is github's target, but not necessarily Matrix's. My dad's never going to go through an edit history, and would probably even miss the "edited by" annotation as it's currently implemented in Riot.
Plus I'm not convinced by "others do it so it's good". I already find it intrusive in GitHub (even though I think it applies better to GH's use case than Matrix's (as Matrix is currently mainly used for, that is)).

A benefit I think nobody has brought up yet is that you can see toxic moderators in action

I'm more in favour of "don't let people cause damage to others" than "let them cause damage and blame them after if someone spots it".

Anyway, I've turned the feature off in Riot and probably won't turn it back on while this is still a thing. It really makes the whole edit feature an anti-feature imho, and kinda makes me too afraid to use it as I don't want to spend all of my time figuring out who posted what part of which message just to make sure I have the right timeline.

@turt2live
Copy link
Member

Ultimately we decided that moderators can't edit other people's messages, though the spec does support it. Closing this as "fixed" given the issue title.

@chagai95
Copy link
Contributor

@turt2live is there a ticket which I can upvoted if I'd like to see admins able to edit messages in the future on Element?

@anoadragon453
Copy link
Member

And if the spec supports it, wouldn't the right thing be for Element web to warn users if it happened?

@turt2live
Copy link
Member

This is largely a spec issue given the MSC recommends this behaviour and is anticipated to stick around for a while.

Please leave a comment on there: matrix-org/matrix-spec-proposals#2676

Locking due to age.

@element-hq element-hq locked as resolved and limited conversation to collaborators Dec 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants