Timeline for Half line answers -- what would be the best course of action(s) to deal with them?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2016 at 7:03 | comment | added | Izzy | I can see that for "outright" (i.e. if you just "stumble upon them"). I however see it a bit different when you get to see it for a flag was risen. Especially with multiple flags ;) | |
| Jan 22, 2016 at 1:41 | comment | added | Matthew Read Mod | @Izzy But it doesn't become not-an-answer by virtue of appealing to advanced users. Lazy answers are worth downvotes, and with enough of them high-rep users can vote to delete, but mods are discouraged from removing them outright. | |
| Jan 21, 2016 at 9:53 | comment | added | Izzy | While I can say "yes" to every single point you say in your answer here, Matthew – IMHO you've forgotten one most important issue with those "short answers": Do they contain enough information to really answer the question – or do they only give a "raw direction"? Taking the example on top, to me it's the latter. It might be an answer to me (I am deeply involved with Android) – but to my dad it'd mean asking 2 new questions: "What is Exposed/Gravity box", "where to find" (spelling error intentional). => it's a lazy comment, not an answer. But can be salvaged in this example. | |
| Jan 20, 2016 at 17:31 | history | answered | Matthew ReadMod | CC BY-SA 3.0 |