LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Once in a blue moon a necro'd thread actually re-opens an interesting discussion. There was one in the Programming section about Armstrong numbers which took on a life of its own and was thoroughly enjoyable and it would have been a real shame if that discussion hadn't happened purely because of some arbitrary age limit on threads.
I think it makes less sense in the context of technical support threads though, and in any case there's nothing to stop a new thread referencing an old one where relevant to the topic.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Personally, I agree with ferrari; I've noticed a number of old threads being re-opened that didn't need to be. I think as said above, if someone feels that an old thread is related to their problem, there's no reason they can't provide a link to it in a new thread. It would mean less confusion for members and mod's alike, and less work for the mod's. I don't think this should apply to the non-technical forum though.
While I *think* I can understand why Jeremy has reservations about doing it, I think the benefits probably outweighs the cons.
I don't know exactly how long it should be until the thread is locked, but maybe a year is probably a good number.
I have the impression that these "lock old thread" suggestions tend to pop up after necroposts by spambots (most recently in here, although the spambot post is now deleted, I think it said "I agree with you" or something meaningless like that). Assuming spambots post randomly wherever they can, the effect of locking threads would be to redistribute their posts to more recent threads. I think this is worse, not better.
For cases where it's humans making inappropriate necroposts, the same people (who are apparently reluctant to make new threads for some reason) might post to current threads instead of old ones, i.e., thread hijacking instead of necroposting. Again, I'm not sure this is better.
By the way, I've seen a few times, where someone comes and gives a good answer to an old unresolved thread. Making a new thread with a reference would not help so much in that case, because that points from answer to question, but there is no pointer from question to answer. I admit this is a pretty rare case though.
i don't see anything wrong with the existing arrangement, i.e. you get warned before posting to a very-old thread.
if anything, that feature could be expanded a little bit to make it harder to overcome for bots/spammers/clueless_noobs.
Every once in a while someone does post to an old thread some new or correct information. I think that anyone looking up a problem needs to watch the dates and versions for answers.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Perhaps, instead of closing old threads, they could be tagged as [OLD THREAD], similar to [Solved]. Or color code the subject area, if thats even possible.
Perhaps, instead of closing old threads, they could be tagged as [OLD THREAD], similar to [Solved]. Or color code the subject area, if thats even possible.
I'd be surprised if it was only the 1000th post
Just wanted to toss it out there.
You should have posted it to one of those old threads instead of making yet another thread about it
Quote:
Originally Posted by ChuangTzu
Perhaps, instead of closing old threads, they could be tagged as [OLD THREAD], similar to [Solved]. Or color code the subject area, if thats even possible.
That might be helpful indeed. In a similar sort of theme of making the necroposting more visible, I once posted a GreaseMonkey script which puts visual gaps between posts proportional to the time elapsed between them. (By the way, notice how that thread was also started in response to a spambot? EDIT: got mixed up, it was this other old thread)
Last edited by ntubski; 07-02-2018 at 08:58 PM.
Reason: wrong thread
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.