Skip to main content

Timeline for How do I flag correctly?

Current License: CC BY-SA 3.0

13 events
when toggle format what by license comment
Jun 12, 2020 at 14:35 history edited CommunityBot
Commonmark migration
Oct 5, 2017 at 7:15 history edited dessert CC BY-SA 3.0
added 4 characters in body
Mar 20, 2017 at 10:32 history edited CommunityBot
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Aug 22, 2016 at 13:44 history edited terdonMod CC BY-SA 3.0
deleted 5 characters in body
Aug 17, 2016 at 14:29 comment added terdon Mod @AndreaLazzarotto more info here.
Aug 17, 2016 at 14:23 comment added Andrea Lazzarotto I see. Thank you for your clarification.
Aug 17, 2016 at 14:06 comment added terdon Mod @AndreaLazzarotto a recent change in the SE engine made it so that you can only flag as VLQ for the first few (7, I think) days after posting.
Aug 17, 2016 at 13:55 comment added Andrea Lazzarotto «Please don't use this flag if one of the others fits» It happened to me once that I couldn't flag something as VLQ but I could use a custom flag. I raised it and it was marked as helpful. What could be the reason of this inability to flag as VLQ?
Aug 13, 2016 at 22:56 history edited terdonMod CC BY-SA 3.0
edited body
Aug 13, 2016 at 22:41 comment added terdon Mod @ByteCommander for those, use a mod flag explaining precisely what's wrong with the answer. The explanation is important since the mod might not notice or simply not know why the answer is dangerous.
Aug 13, 2016 at 19:12 vote accept Byte CommanderMod
Aug 13, 2016 at 19:09 comment added Byte Commander Mod Thanks a lot for your detailed explanation, that is exactly the kind of answer I was looking for. Another small question, if an answer is dangerous (like rm -rf pranks or just suggesting other harmful things, even if intended to answer the question), what would you recommend in this case? VLQ? Mod flag?
Aug 13, 2016 at 17:43 history answered terdonMod CC BY-SA 3.0