# Inability to adds notes to some Flags is a problem

**URL:** <https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643>\
**Category:** Site Feedback\
**Created:** [October 10, 2020, 4:03pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643 "2020-10-10T16:03:15Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 10, 2020, 4:03pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/1 "2020-10-10T16:03:15Z")

</div>

If you Flag a post as " **It’s Off-Topic**" or " **It’s Inappropriate**" there is no ability to add notes to it. The notes would be helpful to both the Flagger & the Moderators.

**"Something Else"** allows further information to be supplied.  
ETA: Added formatting

---

<div class="post-metadata">

**Author:** ![cochrane](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cochrane/32/10441_2.png) [@cochrane](https://boards.straightdope.com/u/cochrane)\
**Post date:** [October 10, 2020, 5:36pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/2 "2020-10-10T17:36:53Z")

</div>

That’s a good suggestion, @What_Exit. I do that all of the time, except when a post is obviously spam. I agree a note helps the mods to see what the issue is and I’m glad to help out.

---

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [October 10, 2020, 9:03pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/3 "2020-10-10T21:03:57Z")

</div>

I’ve reported a lot of posts here on Discourse and so far “It’s something else” is the only choice I’ve ever used.

IMO all the others are simultaneously too specific and too generic for our environment. Except the spam one which seems right-sized for its job. But thanks to our intrepid mods I’ve seen zero spam.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 10, 2020, 9:34pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/4 "2020-10-10T21:34:27Z")

</div>

We get a lot of help from several users reporting spammers and Discourse itself catches a lot of the spammers.

I guess I’ll remember to use Something Else for any Flagging I do. But it would be nice if all of them allows additional notes.

---

<div class="post-metadata">

**Author:** ![puzzlegal](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/puzzlegal/32/3827_2.png) [@puzzlegal](https://boards.straightdope.com/u/puzzlegal)\
**Post date:** [October 10, 2020, 10:21pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/5 "2020-10-10T22:21:02Z")

</div>

Yes, i had exactly the same thought. The note is really helpful.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 11, 2020, 12:00pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/6 "2020-10-11T12:00:13Z")

</div>

Maybe we could disable “ **It’s Off-Topic** ” & " **It’s Inappropriate**". That would also help. These flags just aren’t useful without the ability to add notes.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 13, 2020, 4:16pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/8 "2020-10-13T16:16:26Z")

</div>

@codinghorror could we please either allow the Flags **It’s Off-Topic** ” & " **It’s Inappropriate** to allow & encourage details or disabled this pair.

**Something Else** allows further information to be supplied and is very useful to the mods and better for the users flagging.

It allows for communication of what the problem is and some easy discussion.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 21, 2020, 4:47pm UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/9 "2020-10-21T16:47:27Z")

</div>

Bumping this 8 days later.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/codinghorror/32/4242_2.png) [@codinghorror](https://boards.straightdope.com/u/codinghorror)\
**Post date:** [October 24, 2020, 1:27am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/10 "2020-10-24T01:27:57Z")

</div>

You can certainly **hide literally anything you see on the screen with CSS rules applied to the site’s theme at will** … but this (basically, force everyone to leave comments with all flags _except_ spam?) is a somewhat unusual request I haven’t heard before.

The idea of the “something else” flag is that something nuanced is going on which requires explanation versus “hey staff, please point your attention in this area for a moment.”

I suggest that, before proposing big changes, it might be better to give things a few months to stabilize and for everyone to acclimate to the change in software. To get real world experience and gather data, if nothing else.

(That being said, I am definitely sympathetic to anything that makes moderators’ lives easier – that is, and will always be, an explicit goal of Discourse. If you are seeing a lot of inappropriate / troll flagging, we can advise you about that, but be advised there are already systems in place to deal with that, e.g. staff disagreeing with a flag automatically lowers future flag weight for that person.)

---

<div class="post-metadata">

**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\
**Post date:** [October 24, 2020, 1:36am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/11 "2020-10-24T01:36:12Z")

</div>

> [@codinghorror](#):
>
> … but this (basically, force everyone to leave comments with all flags _except_ spam?) is a somewhat unusual request I haven’t heard before.

AIUI, this isn’t about “forcing” anyone to leave comments when flagging. It’s about _ **allowing** _ someone to leave comments with any type of flag, just as was the case with the old system with the “report this post” capability. Users could still choose to leave the comments field blank if they wished, but at least they would have the option to provide an explanatory comment.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 24, 2020, 1:36am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/12 "2020-10-24T01:36:19Z")

</div>

_ **It’s Inappropriate** _ flag is often hard to tell why it was used. It should have an option of an explanation or not be available.  
The _ **off-topic** _ one is less of a problem.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/codinghorror/32/4242_2.png) [@codinghorror](https://boards.straightdope.com/u/codinghorror)\
**Post date:** [October 24, 2020, 1:40am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/13 "2020-10-24T01:40:21Z")

</div>

> [@wolfpup](#):
>
> as was the case with the old system with the “report this post” capability. Users could still choose to leave the comments field blank if they wished, but at least they would have the option to provide an explanatory comment.

I see, so it’s more of an issue with comparing the old functionality and the new.

> [@What\_Exit](#):
>
> _ **It’s Inappropriate** _ flag is often hard to tell why it was used

Are you seeing global problems with the flag across many different users, or is it more of a user specific issue? How many flags are we talking about, and how often?

I’m not sure how much of that discussion you want to have in public? It sort of depends how much transparency you want around mod actions. In general transparency is a good thing, but when hashing out “how should we handle this” I find that keeping it private (amongst the local staff) is the way to go until there’s a consensus amongst staff.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 24, 2020, 1:42am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/14 "2020-10-24T01:42:50Z")

</div>

The _ **It’s Inappropriate** _ gets used fairly often and its often hard to see what the user thinks is inappropriate. It gets used fairly often, is not specific to any users or groups of users.

The option for comments would be very helpful. Or just not have the option for _ **It’s Inappropriate** _.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/codinghorror/32/4242_2.png) [@codinghorror](https://boards.straightdope.com/u/codinghorror)\
**Post date:** [October 24, 2020, 1:44am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/15 "2020-10-24T01:44:33Z")

</div>

> [@What\_Exit](#):
>
> its often hard to see what the user thinks is inappropriate

Depending on your appetite for transparency, this might be a good thing to have a #Site Feedback topic on. What exactly _is_ inappropriate here? Are the existing rules unclear?

Can specific (and maybe anonymized-ish) examples be provided based on the flags you’ve seen?

All food for thought. In general mod transparency is a net benefit, it can be taken too far but most of the time it’s the _lack_ of transparency that causes problems. (Not saying that’s the case here, just a general observation across dozens or hundreds of other Discourse instances.)

---

<div class="post-metadata">

**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\
**Post date:** [October 24, 2020, 1:48am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/16 "2020-10-24T01:48:14Z")

</div>

> [@codinghorror](#):
>
> > [@wolfpup](#):
> >
> > as was the case with the old system with the “report this post” capability. Users could still choose to leave the comments field blank if they wished, but at least they would have the option to provide an explanatory comment.
> 
> I see, so it’s more of an issue with comparing the old functionality and the new.

Not at all (and, at least from my user perspective, I think overall the functionality of this new system is terrific). The point, rather, is your use of the word “force” as in “force everyone to leave comments”. The existence of a comments field doesn’t have to mean it’s mandatory to fill it in. It shouldn’t be mandatory, in my view. But it’s very useful to have the option.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [October 24, 2020, 1:48am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/17 "2020-10-24T01:48:22Z")

</div>

Well, I’m one of the new mods, so I would have to get the attention of the mod loop on this. I don’t think this board is huge on transparency though. We are big on communication though. I try to get the other mods involved in this conversation though.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/codinghorror/32/4242_2.png) [@codinghorror](https://boards.straightdope.com/u/codinghorror)\
**Post date:** [October 24, 2020, 1:50am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/18 "2020-10-24T01:50:15Z")

</div>

I hear you.

The other thing that’s possible is to edit the copy for the flag – every single word of copy you see in Discourse is editable by the site admins.

(For example, if you wanted to rename the “It’s inappropriate” flag, or change the description of the flag, that’s about 1 minute of work for someone with admin privs on the site.)

The larger discussion about “what is inappropriate here?” is an important one, especially if users are confused about it.

---

<div class="post-metadata">

**Author:** ![Exapno\_Mapcase](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/exapno_mapcase/32/1051_2.png) [@Exapno\_Mapcase](https://boards.straightdope.com/u/Exapno_Mapcase)\
**Post date:** [October 24, 2020, 1:54am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/19 "2020-10-24T01:54:57Z")

</div>

As a user I can’t imagine reporting a problematic post without giving comments on exactly what I think is wrong. I have never used anything other than the Something Else exactly so I can leave a comment. If you think that any post other than obvious spam can be reported without comment, I’d say that’s a serious flaw in the design of the system.

Personally, I’d make leaving a comment mandatory but I can see why some would call just for a button to click on. Still, well, no still. Comments are necessary. Never leave home without them.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/codinghorror/32/4242_2.png) [@codinghorror](https://boards.straightdope.com/u/codinghorror)\
**Post date:** [October 24, 2020, 2:03am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/20 "2020-10-24T02:03:25Z")

</div>

Can’t say I agree with that; if there’s a [Sweet style ballroom blitz](https://www.youtube.com/watch?v=tqketmsRz1E) going on in a topic, merely pointing staff in that direction _should_ suffice.

---

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [October 24, 2020, 11:38am UTC](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643/21 "2020-10-24T11:38:49Z")

</div>

IANA Mod. But IMO most of @codinghorror’s responses to @What_Exit indicate he’s not understanding the issue as we see it. The issue is _not_ “What do we (users or mods) consider inappropriate?”.

The issue, as @Exapno_Mapcase almost said, is that “#1: The current list of canned commentless options is poorly chosen for our culture” and “#2: Given #1, a report without an opportunity for further comment / explanation is nearly useless.”

Not knowing about Discourse’s limits of configurability I suggest:

1. the admins _might_ be able to create a laundry list of maybe 5 or 7 different specific canned commentless options that would suffice for WAG 80% of the reports. With the “something else/other” being the only commented one.

2. Lacking that possibility, it’d be better to simply kill the other commentless options as useless clutter that confuse the users, thereby discouraging reporting. And update the verbiage of the sole remaining commented option to reflect the changes.

Having said all that, let me say _Thanks!_ for how awesome Discourse generally is. This heavy user is very, very happy with the overall experience. Our lack of an admin is certainly not the software’s fault nor that of Discourse’s customer support team.

[Next page](https://boards.straightdope.com/t/inability-to-adds-notes-to-some-flags-is-a-problem/922643.md?page=2)
