Timeline for How to vote on old/dated answers to a question with a now incorrect accepted answer
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2012 at 19:09 | comment | added | Daniel Beck Mod | @ShannonWagner Some kind of "vote to mark as superseded/outdated" that adds a notice to a post might be a good idea. I proposed that in a similar topic a long time ago but it wasn't very visible. It might be time to discuss for a wider audience, but I'm not sure if that problem is widespread on other sites. Non-tech topics aren't usually changing that fast... | |
| Jun 11, 2012 at 19:06 | comment | added | Shannon Wagner | Wikipedia addresses a similar problem with an "as of" template. If information is of the sort likely to become outdated, editors are encouraged to use this template - later editors can easily find information that has been tagged this way (or which has an "expiration date" which is passed). On the one hand, in technology most information eventually expires. On the other hand, we have version numbers on everything so we can often handle expiration. But maybe an "as of" feature would be helpful on SE for cases where information is likely to expire in an unclear way? | |
| Jun 4, 2012 at 13:31 | comment | added | Jeremy W | It looks like some of the answers to the old question have already been cleaned up. I think constructively editing the accepted answer is a great idea. | |
| Jun 4, 2012 at 13:29 | vote | accept | Jeremy W | ||
| Jun 1, 2012 at 18:45 | comment | added | slhck | Yeah, of course I'd mention that something doesn't work or post a better answer instead. It's just that it's hard to get the newest / most correct information to float to the top faster, especially for old and popular questions. But that can probably only be solved by using a metric other than sorting by the accumulated net score :/ | |
| Jun 1, 2012 at 17:56 | comment | added | Daniel Beck Mod | @slhck If you have the time to downvote, you have the time to write "This does not seem to work in $currentVersion anymore." / And many organizations are very slow in updating, even to regular release versions. "Nightly build" might be exaggerated, but if you need to use an older version, you're thankful for answers applying to them. | |
| Jun 1, 2012 at 7:07 | comment | added | slhck | No one mentioned nightly builds. But the question is who you want to target. Of course editing makes sense, but people don't do that too often. | |
| Jun 1, 2012 at 5:53 | comment | added | Daniel Beck Mod | @slhck "just update your production system to the nightly build" cannot be the answer either. People are still running Firefox 2, windows xp, and rhel 4. Voting "this answer is not useful" is misleading. Edit, or add a comment, and move on. | |
| May 31, 2012 at 21:57 | comment | added | slhck | I'm just imagining how I browse Stack sites when I'm looking for help. I'm always annoyed by accepted answers that stick at the top but are terribly outdated. The whole point of SE is to keep signal to noise ratio high and in that case The "built-in warning sign" doesn't help here if the answer just happens to become incorrect. | |
| May 31, 2012 at 18:15 | history | edited | Daniel BeckMod | CC BY-SA 3.0 |
added 285 characters in body
|
| May 31, 2012 at 18:06 | comment | added | Jeremy W | editing seems reasonable. As for sorting -- the average seeker who finds SU may not look past that big green checkmark. | |
| May 31, 2012 at 18:04 | history | answered | Daniel BeckMod | CC BY-SA 3.0 |