LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > LinuxQuestions.org > LQ Suggestions & Feedback
User Name
Password
LQ Suggestions & Feedback Do 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

Reply
 
Search this Thread
Old 04-09-2006, 06:03 AM   #1
Mega Man X
Guru
 
Registered: Apr 2003
Location: ~
Distribution: Ubuntu, FreeBSD, Solaris, DSL
Posts: 5,339

Rep: Reputation: 63
Lightbulb 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...
 
Old 04-09-2006, 06:40 AM   #2
titanium_geek
Senior Member
 
Registered: May 2002
Location: Melbourne Australia
Distribution: it died/ macosx
Posts: 2,478

Rep: Reputation: 50
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
 
Old 04-09-2006, 06:46 AM   #3
Mega Man X
Guru
 
Registered: Apr 2003
Location: ~
Distribution: Ubuntu, FreeBSD, Solaris, DSL
Posts: 5,339

Original Poster
Rep: Reputation: 63
titanium_geek, thanks for the reply mate. Actually, your reply is also a good suggestion:

Quote:
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") ?
 
Old 04-09-2006, 07:15 AM   #4
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 64
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
 
Old 04-09-2006, 07:19 AM   #5
Mega Man X
Guru
 
Registered: Apr 2003
Location: ~
Distribution: Ubuntu, FreeBSD, Solaris, DSL
Posts: 5,339

Original Poster
Rep: Reputation: 63
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

Last edited by Mega Man X; 04-09-2006 at 07:21 AM.
 
Old 04-09-2006, 07:38 AM   #6
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 64
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"
 
Old 04-09-2006, 07:41 AM   #7
Mega Man X
Guru
 
Registered: Apr 2003
Location: ~
Distribution: Ubuntu, FreeBSD, Solaris, DSL
Posts: 5,339

Original Poster
Rep: Reputation: 63
Sounds cool . I've not used the tagging system yet. That thread could certainly get me started. Thanks!
 
Old 04-09-2006, 09:29 AM   #8
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 10,422

Rep: Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628
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
 
Old 04-09-2006, 09:37 AM   #9
Mega Man X
Guru
 
Registered: Apr 2003
Location: ~
Distribution: Ubuntu, FreeBSD, Solaris, DSL
Posts: 5,339

Original Poster
Rep: Reputation: 63
Thanks jeremy for the reply!

The feedback in this forum is just awesome
 
Old 04-09-2006, 02:22 PM   #10
Franklin
Senior Member
 
Registered: Oct 2002
Distribution: Slackware, WinXP, Windows 7
Posts: 1,253

Rep: Reputation: 55
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.
 
Old 03-23-2009, 03:05 PM   #11
johnsfine
Guru
 
Registered: Dec 2007
Distribution: Centos
Posts: 5,107

Rep: Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114
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.

Last edited by johnsfine; 03-23-2009 at 03:12 PM.
 
Old 03-23-2009, 05:44 PM   #12
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728
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.
 
Old 03-23-2009, 06:18 PM   #13
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 10,422

Rep: Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628
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
 
Old 03-23-2009, 06:28 PM   #14
johnsfine
Guru
 
Registered: Dec 2007
Distribution: Centos
Posts: 5,107

Rep: Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114
Quote:
Originally Posted by jeremy View Post
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.

Quote:
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.
 
Old 03-23-2009, 06:32 PM   #15
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 10,422

Rep: Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628Reputation: 2628
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
"Find all threads started by user" not showing all threads Nylex LQ Suggestions & Feedback 3 12-28-2005 08:28 PM
Java threads listed using kill -3 does not contain all threads found using ps -auxww coneheed Programming 2 11-14-2005 08:57 AM
Screen automatically locking gurfrip Linux - Newbie 1 05-31-2005 03:46 AM
Java Threads vs Native Threads rjmendez Programming 0 08-16-2004 05:58 AM
Automatically run screensaver - auto locking screen? nutshell Linux - General 8 02-27-2002 04:08 AM


All times are GMT -5. The time now is 10:29 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration