Locking really old threads automatically?

I've a suggestion. What if you find a way to automatically lock old threads that haven't been touched for 12+ months? They should just be locked, not removed, because maybe they still have important information on them. However, it happens really often in this forum that a newcomer "ressurrect" a 2 yo thread on General for no reason whatsoever. Usually is one of those threads "Windows Vs Linux" or "I hate Linux" kind of thing.

Even if the thread is a serious thread (with a real problem), a 2 years old thread don't add much for the current distributions, considering how fast the open-source development moves.

If locking a thread is not an option, I'd like to suggest at least a "warning" message to when somebody tries to bring one of those oldies back to life, like a confirm dialog or something. I doubt this method would be as efficient as the one with locking old threads, but at least it's something... I guess...

yes. This is an issue, not too bad, but then again, I don't hang out in general anymore. It doesn't help when you search, and have no idea of how old a thread is.

needs some thought- thanks for bringing it up (though more ironically, if you had brought up some ancient thread and hijacked it... )

titanium_geek

titanium_geek, thanks for the reply mate. Actually, your reply is also a good suggestion:

It doesn't help when you search, and have no idea of how old a thread is.

Perhaps defaulting the searches for threads not older then 6-12 months would help a lot as well (the default is "any date") ?

I think this was discussed once before. The best solution I can remember being mentioned was to remove the quick reply box and replace it with a message saying "Please note that this thread is over X months old and has not received a reply in X months, in most cases we would recommend starting a new thread if this is regarding a new issue."

This lets people reply to it using the reply page (which would also include the message) if the issue is still valid but not reply accidently.

There are some old threads that are still valid after such a long time such as the screenshot thread:
http://www.linuxquestions.org/questi...ad.php?t=26643

david_ross:

Thanks. That is one of my favorite threads on General. A few screenshots there could be considered "art" . Still, I mean to lock untouched, dead old threads where nobody is posting anymore. The screenshots gets one post almost everyday, so it's very alive.

Good idea about the quick reply box by the way

Sounds like you've just come up with another good use for the new tagging system - next time you see a screenshot that you like, just tag it "art"

Sounds cool . I've not used the tagging system yet. That thread could certainly get me started. Thanks!

I've added the "no quick reply + message indicating old thread" to the bug tracker. This looks like a feature we missed porting during the code upgrade. Thanks for the suggestion.

--jeremy

Thanks jeremy for the reply!

The feedback in this forum is just awesome

I was going to post a suggestion, but this seems an appropriate thread to place this in.

I was just thinking that it would be nice to know when a particular thread was started without opening it. You currently post the name of the OP, but I think it would be nice to see the date of the first post next to th OP's name as well. The time is not important as I would like mainly to know at a glance if a 3 year old thread has been bumped by someone that was not paying attention.

The suggestions you have offered above seem like a start, but I still think this would be helpful.

My 2 cents.

Instead of starting a new thread requesting better guards on old threads. I'll just tack this onto on old thread on the subject.

Whatever happened to this topic?

I guess the Quick Reply area was missing when I went to reply to this thread, but that wasn't enough of a warning. Nothing really rubs my nose in the fact that I am resurrecting a dead thread. I need more of a clue (I can be a bit dense).

But actually my problem was in this thread:
http://www.linuxquestions.org/questi...20#post3485320

Someone else added an answer to the end of dead thread. So I thought it was a new thread. I thought all the answers missed the point so I added a better one. Only after posting I realized it had been a dead thread. (So I edited my response away).

I know at some point automation can't substitute for intelligence. Some dead threads are legitimately reopened.

But I've made this same mistake a few time before (follow on after someone posts a new answer to a dead thread).

It would be great if you could think of some way to highlight the first post after a long gap in time as such, so anyone reading the thread is reminded to notice the dates in case they matter. So after someone makes the mistake CrazyToon made in that thread, someone else won't follow.

It also would be nice to discourage the original mistake a bit more clearly.

Can you change the "Post Reply" button to a "Reopen Old Thread" button when the last post is really old? The button could do exactly the same thing as "Post Reply" just look different.

Since this topic has been resurrected, I'll suggest that any thread over 2 years old should be closed automatically. I just watched a newcomer--in good faith--adding some helpful words to a 4.5 year old thread----I'm pretty sure that none of the original participants have been around for awhile.

As mentioned, we already disable the QRB for old threads. I'd have no problems also including some big bold note or even AJAX popup indicating the thread is old on a new post submit. That being said we have no plans to lock old threads indiscriminately. It's not really inline with the LQ way of thinking.

--jeremy

Originally Posted by jeremy I'd have no problems also including some big bold note or even AJAX popup indicating the thread is old on a new post submit.

Hopefully you mean something one would see before typing the response, not on submit.

Anything that makes it more obvious could cut down that error. But I think simpler is better.

Since you're already rid of quick response, your remaining focus should be on the "Post Reply" button. I'll repeat my suggestion in case you missed it, to change the text inside that button when the last post is over age X.

If you don't like that idea, I hope you can put something either near enough that button you can't miss it or first pop up after you press that button.

That being said we have no plans to lock old threads indiscriminately. It's not really inline with the LQ way of thinking

Glad to hear it. I would not suggest taking away the ability to reopen a stale thread. Just take away the ease of doing it by accident.

From a UI perspective, I would probably have the text box after clicking "Post Reply" be greyed out with a note explaining the thread was old, along with a dismiss button - but I'm open to further feedback on that.

--jeremy