Too hot on locking Threads

Question

Dang it Rukbat, you locked a revivified thread I was replying to.  Back off a little.  Not every old thread is really finished.  Since I can't post the reply there, I'll post it here.
There's a real problem with trusting and verifying information from the internet.  The problem increases with age; you don't know if it still applies.  Yes, there is still adump etc., but it needs to be considered in the context of adcri in modern versions... Even on MOS you see "applies to version..." or other statements implying it has been recently vetted, but that's often misleading.  The official docs don't really have good change management visible.
People who write quality Oracle books still will have jobs for a long time to come.

Answer 1

I agree with your opinion.  I partly disagree with the moderator action of jumping on it and locking it.  It's a content question as to whether it should be locked, which means the moderator has to make a content decision as to whether anything new can come of it - and in this case, I was pointing out the aging error, which would be missed by simply locking it, so that turns it into an incorrect content decision.  I agree inasmuch as most revivification is simply dumb - but the post in question explicitly noted the age of the thread, that should be a "get out of jail free" card.
It's also frustrating composing a reply in a forum whose software hasn't settled down yet, only to get a "you are not allowed to post in the space" error.