# 효과적인 플래그 무결성 관리 부재

**URL:** <https://meta.discourse.org/t/lack-of-effective-flag-integrity-controls/279246>\
**Category:** Community Building\
**Created:** [9월 16, 2023, 6:35오후 UTC](https://meta.discourse.org/t/lack-of-effective-flag-integrity-controls/279246 "2023-09-16T18:35:01Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)\
**Post date:** [9월 16, 2023, 11:46오후 UTC](https://meta.discourse.org/t/lack-of-effective-flag-integrity-controls/279246/17 "2023-09-16T23:46:37Z")

</div>

이것이 폭발적으로 증가하는 하위 주제와 관련이 있다면, 이쪽으로 옮깁시다

> [@토픽 내 하위 토픽 과다 생성 방지 방법](https://meta.discourse.org/t/how-to-avoid-an-explosion-of-sub-topics-in-a-topic/279257):
>
> These are my thoughts, with an implicit question of how members and mods might respond, when a thread starts to go exponential. Discourse doesn’t offer threaded discussions, although it does have a sort of back-pointer, in the case that a post is a reply to a previous reply. It also allows for quotes from previous replies. Overall, if a topic has more than a handful of replies already, it’s possible that the next reply will be a general response to the topic, or to the head post a specific …

---

_[View the full topic](https://meta.discourse.org/t/lack-of-effective-flag-integrity-controls/279246)._