From my experience it happens just as much on forums. Hell, just take a look at Stack Overflow! If someone is wanting to reanswer a question for the nth time, I have no problem with that, and the helpers in my community don't either. As another poster said, as well, sometimes "repeat questions" age out after a certain point, where a newer method is actually more appropriate than an older one anyway.

"As another poster said, as well, sometimes "repeat questions" age out after a certain point, where a newer method is actually more appropriate than an older one anyway."

I rather like the approach of editing the original question/solution or posting the latest solution there as otherwise this just creates fragmention.

> I rather like the approach of editing the original question/solution.

I believe we need the history, especially when dealing with legacy versions. The first thing I usually check is the date or contexts to infer it.

That's somehow even worse than doing support on Discord, where at least there is a history and the (bad!) search or one of the regulars might remember something to find it.

> If someone is wanting to reanswer a question for the nth time, I have no problem with that

But I do have a problem with having to ask a question that has already been answered a hundred times, instead of being able to search for the answer.

This is a great point, especially since its a metric thats extremely difficult to track, if at all