I certainly didn’t have that extreme of a reaction, that’s not charitable. But yes, I felt quite surprised about the idea that staff couldn’t be flagged and hidden. At the very least, it seems there should be an alert, else it seems like a bug.
To be clear we never tested self-flagging in this case. It was just a way that @Dax figured out how to reproduce our experience. We were only flagging each other’s posts where we all happened to be staff.
Our actual intention for flagging is the hide+edit process and to make that so fast and easy and common and normal that flags are not seen as a big negative, just a normal part of everyone in the community checking each other to stick to the highest standards by our guidelines. So, in that view, there’s no reason staff would be immune. In our approach, you would have flagged me to fix my overreaction instead of replying here, polluting the topic… (and I’ve since edited my badly-written post above and hope this part of the exchange doesn’t hurt the valuable part of this topic… but it’s on-topic in that I’ve proven that I could be a staff member somewhere, though I’m not here, and yet post carelessly enough at times…)
So, sincere apologies for overreacting. And no need to get @eviltrout involved (unless they would know especially about the outstanding bug, see below), I saw there is a checkbox in the settings, and I even recall seeing it when we set things up. We have it checked to allow staff flagging.
Remaining bug (that is a real issue, not just nonsensical test case)
- Post as one staff account
- Make sure the checkbox is checked to allow staff to be flagged
- Log in as another staff
- Flag via “Take Action” button
- see the same blink and non-hiding as reported above
So, we allow staff posts to be flagged. We have latest version of Discourse. The “Take Action” button is failing to work as expected for a normal case of a (staff) user flagging another (staff) user.