undefined | Better HN

0 pointsjasode2y ago0 comments

>So would be much more useful if there were some effective mechanism to get rid of or correct entries that were answered incorrectly in the first place or have become incorrect or no longer relevant with time.

Sometimes, the community will "fix" that by having a newer answer get upvoted beyond the "accepted" answer. E.g. a Python 3.2 answer with more modern syntax in 2014 gets upvoted above the Python 3.1 accepted answer in 2010:

- https://stackoverflow.com/questions/2331592/why-does-datetim...

But that type of "correction" only happens on popular questions. The more obscure questions and answers that are wrong will remain wrong because there are not enough eyeballs and/or widespread expertise to fix them.

0 comments

1 comments · 1 top-level

arp2422y ago

I answered a popular-ish Ruby on Rails question in 2014 and it's still 3 votes shy from overtaking the outdated top answer from 2009. I don't even know if my answer is the best today because I haven't done Rails in years.

I definitely think this is a major pain point in the platform. I don't think that doing away with duplicates is the answer – instead there should be a way to downrank outdated stuff. Or something. I think they were experimenting with some approaches, but I haven't really been active in the last few years.

j / k navigate · click thread line to collapse