Timeline for Custom comment flags should not auto-delete comments or be automatically marked helpful
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5 at 23:41 | history | edited | Ryan M | CC BY-SA 4.0 |
All of these are now verified (at least, U/U flags are marked helpful on post deletion), so remove the annotations indicating which ones are and aren't; add an example
|
| Jun 20, 2023 at 20:30 | history | edited | Ryan M | CC BY-SA 4.0 |
Clarify that automatically marking the flags helpful is also a problem.
|
| Aug 24, 2022 at 3:38 | history | protected | CommunityBot | ||
| Aug 11, 2022 at 8:09 | comment | added | Sonic the Anonymous Hedgehog | @CodyGray Also, normal users will most of the time save time by just choosing a canned flag option rather than a custom one. Custom ones are few and far between, so no meaningful amount of time will be saved by just making it go away. | |
| Aug 11, 2022 at 5:50 | comment | added | Cody Gray | Precedent is clear; we don't do it for custom post flags, so why do it for custom comment flags? Also, custom comment flags raised by mods don't auto-delete. The obvious objection to this would be scale, something along the lines of "if the comment can just go away, without anyone else having to look at it, then isn't that going to save everyone time?" Well, if you have two Stack Overflow moderators supporting this, you aren't likely to prevail on the "scale" argument. | |
| Aug 11, 2022 at 1:56 | history | asked | Ryan M | CC BY-SA 4.0 |