# Vicious flagging/editing cycle

**URL:** <https://meta.discourse.org/t/vicious-flagging-editing-cycle/36572>\
**Category:** Bug\
**Created:** [12월 11, 2015, 3:20오후 UTC](https://meta.discourse.org/t/vicious-flagging-editing-cycle/36572 "2015-12-11T15:20:45Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![rxc](https://avatars.discourse-cdn.com/v4/letter/r/22d042/32.png) [@rxc](https://meta.discourse.org/u/rxc)\
**Post date:** [12월 11, 2015, 3:20오후 UTC](https://meta.discourse.org/t/vicious-flagging-editing-cycle/36572/1 "2015-12-11T15:20:46Z")

</div>

A problem with the way community flagging works [as previously described](https://meta.discourse.org/t/so-what-exactly-happens-when-you-flag/275)…

While a moderator isn’t around, watching like a hawk, this causes a two-part problem:

1. A user can do the bare minimum of editing by adding/removing a couple words to get his (completely unacceptable) post unhidden.

2. The users who flagged the comment, now can’t re-flag the slightly-edited comment because they flagged the original version and their “undo flag” option is now gone.

You may not have enough TL1+ users on a low-traffic topic to again hide the unacceptable comment, and it stays up (i.e. all weekend, with angry users responding) until an editor comes in to take a look.

---

_[View the full topic](https://meta.discourse.org/t/vicious-flagging-editing-cycle/36572)._