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.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,605
Rep:
The vast majority of the cases you're referring to actually find the threads via an external search engine, not LQ's. That said: 1) There is a limit on search terms on the internal search and 2) You should be seeing *much* less spam recently here at LQ, as some changes/additions have been highly effective.
Not to flog the horse continuously, I was ready to post yet another variation of complaint/question/suggestion, and did a search in the feedback forum to find this conversation.
This other thread http://www.linuxquestions.org/questi...-files-139554/ was raised up this morning and I evaluated it. Went all the way back to the beginning to determine what the original problem was and noticed that the OP never had returned. Then I began to notice the timestamps, 2004, 2007, 2009-2011. "How to run an executable file" I mean ... helpful as archive? Yes.
The present person to resurrect it did so as their first post.
I fully get that they were shown the graphical warning about resurrecting an old post, but they still did so and they're new, they may be a fine eventual contributor.
It's unclear whether or not they were asking a question, see reply #32.
Not sure if there are things in there versus not and for some it would go against the grain in a major way, plus cause extra work for someone. But maybe the first few posts of a new user could be entirely moderated (I think Stack Overflow does exactly that) so as a result, a poor judgment posting can be stopped from perpetuating the resurrection of a very old thread, or also stop spam.
The present person to resurrect it did so as their first post.
I fully get that they were shown the graphical warning about resurrecting an old post, but they still did so and they're new, they may be a fine eventual contributor.
It's unclear whether or not they were asking a question, see reply #32.
A first post which is pretty much a complete non-sequitur: %99 chance of spam bot.
Maybe a compromise? Any new post to a thread older than a set time will need to reviewed by a moderator before it gets posted?
I guess it depends on how often someone resurrects a thread. If it's a common occurrence, I don't think we should expect the mods to manually filter through all of them. On the other hand, if it only happens 1 or 2 times a week, it seems like a more reasonable proposition. Stickies should probably be exempt from this, like the Linux vs Windows thread.
And then there's that lightbulb thread that keeps popping up...
Just my
Last edited by maples; 03-27-2015 at 12:42 PM.
Reason: typos
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,605
Rep:
Quote:
Originally Posted by smeezekitty
Some forums display a big red message when replying to an old thread while still allowing it. Maybe that's
an idea?
For old threads the quick reply is completely disabled and there's a large bold red message that says "Please note that this thread has not been replied to in over 6 months. Please ensure your reply is still relevant and timely".
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,339
Rep:
Quote:
Originally Posted by jeremy
For old threads the quick reply is completely disabled and there's a large bold red message that says "Please note that this thread has not been replied to in over 6 months. Please ensure your reply is still relevant and timely".
--jeremy
Oh. I guess I didn't realize it because I generally don't try to reply to old threads.
For old threads the quick reply is completely disabled and there's a large bold red message that says "Please note that this thread has not been replied to in over 6 months. Please ensure your reply is still relevant and timely".
--jeremy
Sure but what I'm talking about is a thread resurrected by someone's first post. So they don't know the rules too well. And that thread was re-resurrected 3 or 4 times over a 10 year period.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.