Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Today, on apple mailing lists, someone said:

Keep in mind that out-of-date information never gets removed from StackOverflow. It's a treacherous place to use as your primary source of information.

I believe, we all come across such Q/A frequently. Updating them is a huge task. However, marking/signaling the answers as outdated could be useful.

It could be presented in the form of a visible message telling that the information might be outdated. The number of users that did report the post outdated could also appear. There may also be other ways to proceed. Just some thoughts.

For instance, for those who need to check Apple's documentation, APIs, sample code… they have such system. It is limited, but effective at telling some content is outdated.

share|improve this question
But outdated does not necessarily equate to "no longer useful". What about those who have to maintain legacy code? – Bart Mar 23 '13 at 0:03
That's why we can edit posts, and if enough people edit it will become wikied and end up being maintained by the community. There are many posts that are already like that. A post if it is outdated just needs to get the ball rolling by having someone update it. – cryptic ツ Mar 23 '13 at 0:04
Of course. That's why I wasn't talking about deleting them. Flagging these question as outdated may actually help users by telling them there are more up-to-date solutions. – Jean Mar 23 '13 at 0:05
Then you might want to clarify that in your request. Because flagging is usually meant to bring something to a moderator's attention. – Bart Mar 23 '13 at 0:07
@Bart Ok. Sorry then. Is "marking" a more suitable word? (I am not native speaker) – I edited my post. thx. – Jean Mar 23 '13 at 0:08
So, what? Would we just base this naively on the date/time stamps? Or would we have some of marking the question as "outdated"? If so, who would do that? Would it require a consensus vote? A moderator? How would those people make that decision? Would we require them to be experts in the field (e.g., based on tag reputation)? Would the decision to mark be reversible? Would anyone even read the message if we had one displayed? (Hint: no) – Cody Gray Mar 23 '13 at 0:14
And wouldn't this take away from the primary goal/expectation that when experts come across an answer with outdated information, they edit the answer to update it? – Cody Gray Mar 23 '13 at 0:14
No it wouldn't. Editing all of them is a huge task. So, pending editing, they could be marked/tagged/signaled… Wikipedia does that, so that while the article waits to be edited, others can know. And it can also help the editing process by identifying what needs to be done. It wouldn't be based on timestamps, but on "flags" by those who did recognize the out-of-date info on the text. – Jean Mar 23 '13 at 0:16
I guess, reaching a certain amount of reputation, users would gain the possibility too mark outdated content. The number of such "flags" would be displayed in the message. Readers could then make up their mind "careful, 8 users have marked it as outdated… this may no longer be the solution to this issue"... – Jean Mar 23 '13 at 0:20
@Jean: How would the removal of such flags be (efficiently) orchestrated following an update? – Pieter Geerkens Mar 23 '13 at 3:13
Once an edit is made, the users that did mark the post as outdated would be notified, so they come back and check the edit to remove their outdated vote, if they deem so. I believe those who did mark the post as outdated to be the more qualified to decide wether or not the update does indeed solve the issue. Some question, however will stay outdated forever. – Jean Mar 23 '13 at 11:37
A similar thing was asked in "Evolving Subject Q&As are outdated" with a more extreme suggested solution. As I argue there, I don't think the rate of obsolescence for Apple-related development technologies is as fast as people assume. The vast majority of answers in [ios] and [cocoa] left three or four years ago still seem to apply. The person you quote there may have a mistaken impression of the site based on one or two problematic questions or answers. – Brad Larson Mar 23 '13 at 21:47
Highly possible, I agree. However, while the second sentence is purely subjective and may or may not be based on too few experiences, the first one is a fact. And as technology evolves, it can only get worse. The importance of the need to take action purely depends on the number of such outdated answers and their impact. Left to the community to decide what action should (or shouldn't) be taken. – Jean Mar 23 '13 at 22:26
By depends on the number of such outdated answers and their impact I mean that an outdated answer to an outdated question probably isn't an issue. The real problem is outdated answers to current questions. APIs get deprecated, replaced. Vulnerabilities discovered, and advices on best practices may evolve... – Jean Mar 23 '13 at 22:29
How ever, (I read all comments) I - still - think that a flag or mark for (possible) outdated threads, would be usefull; just a mark in "related questions" and/or a mark when opening the question, not delete or filter, just a hint for silly ones like me, reading a simillar question as I have, ending up in 'with IE5 it will be corrected" ... – halfbit Nov 9 '13 at 20:23

Practical case

In this thread Firefox can't establish a connection to the server at ws://, there was an issue about real-time exchange method between browser (client) and sockets...stackexchange (server).

This kind of technology is something new and the question was about a specific browser: Firefox, but in a specific version (v12 on XP).

Without real answer to this question, by normal evolution, newer versions of Firefox (now I use version 22 of Firefox) has this bug corrected.

So I agree with that simply dropping the thread is not a good idea, but I think that adding a little header, like this:

Outdated - 2013-05-28

because there is new versions of tool/libraries where the bug don't exist anymore

I've already do this on my answer: I'm using Firefox 17.0 (french..., but I don't now if I could write this on the top of the question. Maybe in a SE standardized form.

I think that this could become a special SE feature.

share|improve this answer
+1 Maybe in a SE standardized form, a special SE feature → Just like Wikipedia does. You get standardized, highly relevant, warnings about all kind of things, showing up at the top of the article. – Jean May 28 '13 at 11:18
Another example: – psoft Nov 28 '13 at 17:48
Another example - it's outdated according to this comment. – BartoszKP Feb 3 '14 at 14:19

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .