Skip to main content

Timeline for Make comment flags less stupid

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
Apr 7, 2015 at 0:19 comment added Shog9 Mod Not gonna use "unconstructive" unless we can make it "deconstructive" on Philosophy.
Apr 6, 2015 at 12:53 comment added Tim Yeah, I see your point about tooltips being redundant...
Apr 6, 2015 at 12:25 comment added James @Tim I agree the first one is redundant, but if you have the second one because it is the entire point of my suggesting them (to show users this new flag is now for the old ones - unconcstrictive, obsolete etc), then you have to have them all really. A description on one and not the others will look "unfinished" and "might" bring confusion. Tooltips are not immediately obvious, and can be missed
Apr 6, 2015 at 12:21 comment added Tim The first explanation is umm kind of redundant. The second one I can see as useful. Maybe as a tooltip?
Apr 6, 2015 at 11:23 comment added James @tchrist Fair enough - it was just a crude example tho, Stack wouldn't be using the text I write, they'd use their own. Was more to show the idea of listing the old close reasons within a new one - so people can see "what do I use for obsolete now - oh, I see"
Apr 6, 2015 at 3:37 comment added tchrist s/the above two/the other two/
Apr 6, 2015 at 1:10 comment added WetlabStudent Actually "unconstructive" might be better than noisy. I kind of think obsolete and too chatty are examples. Noisy is in my opinion too technical.
Apr 6, 2015 at 0:39 comment added WetlabStudent If we do reduce the number of options, the summary is necessary. A lot of people will have no clue what "noisy" even means (especially for less technical stackexchanges)
Apr 5, 2015 at 23:57 history answered James CC BY-SA 3.0