Replying too quickly when flagging a post

pr-welcome

(Rob Nicholson) #1

I’ve just flagged my own post further up a topic just after typing a new reply as “Something else” to ask the moderator to split the topic. I took the time to suggest a new topic title. Discourse annoying threw away my flag saying I was replying too quickly. I had to wait a minute or two and then type it all in again. I don’t think that check should apply to reporting a post.


(Andrew Waugh) #2

Were you trying to flag the post within the “editing grace period” in /admin/site_settings/category/posting?

I’m not sure of how it is actually coded, but from a design standpoint it makes sense to me that mails don’t go out, edits aren’t saved as revisions, and flags are disabled until that grace period has expired… otherwise it isn’t much of a grace period.


(Rob Nicholson) #3

No problem with the concept of replying too quickly to actual posts but this is something different. It is most likely at the point of replying that you’ll say to yourself “this topic needs splitting”. It certainly should not throw away my hard-typed reason for flagging.

PS. Although one wonders how effective the two nags of replying too fast or not including enough text in a reply are. I suspect most just pause for a few minutes and still reply and we definitely get “…” at the end of short posts.


(Andrew Waugh) #4

We don’t get all that many people padding their posts, but the number of “Body is too short (minimum is 20 characters)” I see in /admin/email/rejected is pretty high. Most of them are “Thanks Wally.”, “I agree.”, “Yes.” or “Amen.”. Our users don’t use “Thanks” much.


(Jeff Atwood) #5

Sorry, I am unable to understand what you’ve written here? What are the steps to reproduce, exactly?


(Rob Nicholson) #6

Pretty much what I said in my post…

  1. Typed a reply to a topic
  2. Realised it had wandered off-topic a few replies back
  3. Scrolled up to where it went off topic
  4. Flagged the post as “something else” and typed in why
  5. Clicked OK

Discourse message saying I was replying too quickly came up and threw my report away when I clicked OK. Had to wait a minute and do it again.


#7

This is because flagging a post as “something else” causes a private message to be sent to moderators with a link to the flagged message and the information you give, “something else”.


(Sam Saffron) #8

I support having a custom error message for this specific case.

“Please wait a bit longer prior to flagging this post”

Or something along those lines

#pr-welcome


(Rob Nicholson) #9

I still maintain this message should not appear at all.


(Joshua Rosenfeld) #10

I’d agree it’d be nice to not have the message thrown away, but I disagree that there should be no rate limit at all. Allowing infinite flagging (especially with group PMs involved) just opens us up to spamming.


(Tushita Rathore) #11

Can I work on this bug, such that the custom error message is shown?
@sam


(Sam Saffron) #12

Sure, go for it !:smile:


(Rob Nicholson) #13

I’d still prefer the time check to be removed on the flagging mechanism. It makes no sense in this scenario IMO. Just had it again. Threads often wander in a discussion about beer which was obvious as I was just composing a reply to a topic. So the first thing I did was flag my own post as needing a topic split. To make me wait 30 seconds (or whatever) is plain annoying because I’m always going to still flag the post. It won’t make me reflect on whether I should be flagging it will it?

But if you don’t accept this, then yes please fix the bug where it throws away comment when using “Something else”. That’s definitely a bug. A user interface shouldn’t throw away a typed response without being able to correct it.