In our community moderators like to use the new awesome slow mode to keep things calm when a topic goes sideway. More precisely, someone flags an aggressive post, we moderators accept the flag, and then we put the topic in slow mode, asking in a public response for corrections of all aggressive posts before disabling the slow mode.
But this does not work. Because users cannot edit old posts in a slow topic.
Is there any workaround? Is it possible to configure the slow mode so that editing old posts is allowed?
Very much appreciate you raising this issue, @Elvith ā Iāve been following along with the discussion of āSlow Modeā since it was introduced, and we immediately started using it in many places in the community Iām part of.
(For context, many of our users are arriving from some frankly-toxic mailing lists that our Discourse forum is replacing, and they are in very bad, repeatedly-validated-on-the-mailing-lists habits of engaging their keyboards before hearts or their brains when things start getting heated).
@codinghorror (and anyone from the Discourse team whoād like to comment) ā our experience on our forum matches @Elvithās, where the current behaviour means that āSlow Modeā interferes with the moderation workflow: folks canāt edit their posts to bring them within guidelines, whether in response to auto-hiding after a sufficient number of flags, or even when moderators actively hit āAgree + Hideā.
Would yāall accept a PR to add a site setting to determine whether āSlow Modeā prevents edits, so that folks like myself and @Elvith can restore the request-to-edit behaviour, and take our chances with āedit warsā? If so, would you want to see those edits counted as someoneās post in the topic (i.e. only allowed as frequently as their posts would be), or would it not make a difference in that you donāt personally foresee using this?
Because users cannot edit old posts in a slow topic.
Of courseā¦ I donāt have the skills to do those so the language isnāt very present in my mind!