How to prevent revival of old threads from the dead
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.
How to prevent revival of old threads from the dead
At occasion it happens that an old thread gets revived. However, recently there seems to be a huge increase in this.
I suggest that we try to find a solution for this. One possible way is inform the new poster that the last post in a tread is e.g. over a month old.
Quote:
The last post in this thread is over one month old; if you feel that your reply helps to solve the problem or that the starter of the thread will still benefit from your reply, feel free to post.
To make posting to an old thread a little bit more difficult, the quick reply can be disabled for those threads.
The conditions can be finetuned (e.g. solved threads do not allow posting at all after the expiry period and threads over a year old also do not allow posting).
Last edited by Wim Sturkenboom; 09-06-2009 at 01:49 AM.
Sometimes a solution for an unsolved problem is found a long time after the last post in a thread. In that event it is helpful to post the solution otherwise someone netsearching a problem may find the old thread and wrongly believe there is no solution.
IIRC the quick reply box is removed for threads older than n months. Posting solutions in dormant threads is acceptable, unfortunately some people revive threads just to ask questions as easily. Since closing petrified, mummified, dead or geriatric threads isn't an option and if people don't take quick reply box removal as cue I wonder if they will notice any added warning signs even if in bold 31 pt font size text with blink tags ;-p
I offered the "close thread" option because it is often offered as a "solution" but not acceptable to LQ. And while closing threads is a last resort option strictly guided by rules, yes, sometimes there are good reasons for doing that. Me wondering if adding a text warning will work is not based on my personal subjective opinion of doing that but on seeing how people deal with reading text in general and in the context of LQ. But let's see what Jeremy will say...
The conditions can be finetuned (e.g. solved threads do not allow posting at all after the expiry period and threads over a year old also do not allow posting).
While I agree that the aforementioned message may be helpful in reducing unnecessary thread revival, I don't believe disallowing appendages with updated info would be helpful at all. One can find outdated, useless information anywhere.
And re-reading my post I see that I indeed mention closing (in different wording) in the finetuning part.
For the solved threads I still consider that OK; although many roads lead to Rome, one way is enough (after that period). Reconsidering the second example, I'm no longer behind that.
I remember the time I revived a zombie... "huh. quick reply must be broken. oh well, click through to 'reply'" later: "ooh, there is a thread here muttering *braaaains*"
Maybe when the quick reply box is removed, a note explaining why it has been removed might help.
Maybe when the quick reply box is removed, a note explaining why it has been removed might help.
That might help for some (most?), but I don't even look for the Quick Reply box. I use Quote or Post Reply, as I prefer the advanced editor.
unSpawn is partly right, too... Even a popup box will be ignored by a few (some people click OK without actually reading the message), however, I do still feel that it would be more effective.
I blame that "ok ok, I know what I'm doing" click without reading thing on two things: this impatient micro-wave generation, and windows (even before Vista.)
heh: maybe a question that the user has to answer before continuing: (easily found in the text.) Ie: posting in this thread would mean what kind of thread? (answer: zombie) after explaining what the old post is. (Not a serious suggestion.)
/end tangent
titanium_geek
Last edited by titanium_geek; 09-08-2009 at 12:08 AM.
I think a bit of data validation will make that more difficult. I'm not sure if that's already implemented as I never post threads with a title like that
Titles consisting of a single word can be prevented and maybe 'forbidden' keywords.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.