LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 02-09-2011, 06:39 AM   #1
GazL
Senior Member
 
Registered: May 2008
Posts: 3,502

Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024
[RESURRECTED] Thread prefix?


When some muppet comes along several years after a thread is dead and bumps it, people tend not to notice the time disparity and can end up wasting time re-reading/responding to posts that have long since lost their meaning.

How about a new prefix that is automatically applied to a topic title ( just like [SOLVED] ) when a thread is brought back from the dead so that people aren't caught by surprise.
 
Old 02-09-2011, 07:17 AM   #2
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,135
Blog Entries: 52

Rep: Reputation: Disabled
Yeah, it's a problem. The worst I've seen was 8 years old. Maybe a prominent banner somewhere saying "Please check the thread's age before replying" is the solution.
 
Old 02-09-2011, 07:52 AM   #3
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,596
Blog Entries: 1

Rep: Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046
... or an automatic closure of a thread that hasn't been updated for a year.
 
Old 02-09-2011, 08:13 AM   #4
GazL
Senior Member
 
Registered: May 2008
Posts: 3,502

Original Poster
Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024
Quote:
Originally Posted by sycamorex View Post
... or an automatic closure of a thread that hasn't been updated for a year.
Sometimes there's a valid reason to update an old thread, my suggestion was more about increasing visibility of the fact that the thread is an old one.

Last edited by GazL; 02-09-2011 at 08:14 AM.
 
Old 02-09-2011, 08:44 AM   #5
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,596
Blog Entries: 1

Rep: Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046Reputation: 1046
Quote:
Originally Posted by GazL View Post
Sometimes there's a valid reason to update an old thread
Theoretically yes, but practically I can't see any valid reason for an update of, say, a two year old thread (apart from the general non-technical section). In 99% of cases it'd be more reasonable to start a new thread. It saves time for everyone:
a) members/mods will not waste time on looking at such a thread again.
b) members/mods will not waste time on writing things like: Please don't resurect a x-year old thread / Please don't hijack a thread. Start a new one, etc.
c) in the very unlikely case that there's a valid reason to make a post in such a thread. One can always start a new thread and link it to the old one.

IMO, the number of b) is MUCH higher than the number of c)

On the other hand, I like the prefix idea as well.
 
Old 02-09-2011, 08:59 AM   #6
TheIndependentAquarius
Senior Member
 
Registered: Dec 2008
Posts: 4,633
Blog Entries: 29

Rep: Reputation: 897Reputation: 897Reputation: 897Reputation: 897Reputation: 897Reputation: 897Reputation: 897
Once while searching Google, a TWO year old thread came up but didn't have the "command" required for the desired solution, so I searched further and found that "command"! The first thing I did then was to reply to that two year old thread stating the reasons and the command in question, the next day some member of that thread acknowledged my post, rated helpful and said a thankyou,

Crux: Closure is not always the solution.
 
1 members found this post helpful.
Old 02-09-2011, 10:04 AM   #7
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 10,623

Rep: Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657
Quote:
Originally Posted by brianL View Post
Yeah, it's a problem. The worst I've seen was 8 years old. Maybe a prominent banner somewhere saying "Please check the thread's age before replying" is the solution.
There's actually a message *and* the Quick Reply is disabled.

--jeremy
 
Old 02-09-2011, 10:05 AM   #8
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 10,623

Rep: Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657
Quote:
Originally Posted by GazL View Post
How about a new prefix that is automatically applied to a topic title ( just like [SOLVED] ) when a thread is brought back from the dead so that people aren't caught by surprise.
Out of curiosity, how big of an issue do long time members feel this is?

--jeremy
 
Old 02-09-2011, 10:07 AM   #9
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 10,623

Rep: Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657
Quote:
Originally Posted by Anisha Kaul View Post
Once while searching Google, a TWO year old thread came up but didn't have the "command" required for the desired solution, so I searched further and found that "command"! The first thing I did then was to reply to that two year old thread stating the reasons and the command in question, the next day some member of that thread acknowledged my post, rated helpful and said a thankyou,

Crux: Closure is not always the solution.
This is one of the many reasons I'm against auto-closure. Continually telling new members they should search before the post and then closing all older threads just doesn't seem right IMHO.

--jeremy
 
Old 02-09-2011, 10:15 AM   #10
goossen
Member
 
Registered: May 2006
Location: Bayern, Germany
Distribution: Many
Posts: 224

Rep: Reputation: 41
Quote:
Originally Posted by Anisha Kaul View Post
Once while searching Google, a TWO year old thread came up but didn't have the "command" required for the desired solution, so I searched further and found that "command"! The first thing I did then was to reply to that two year old thread stating the reasons and the command in question, the next day some member of that thread acknowledged my post, rated helpful and said a thankyou,

Crux: Closure is not always the solution.
I agree! Many times I found old threads from this forum while searching, and many of them are "not solved". I agree the solution won't be more needed by the OP but people searching will be benefit.
 
Old 02-09-2011, 10:32 AM   #11
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,563
Blog Entries: 29

Rep: Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179Reputation: 1179
Quote:
Originally Posted by jeremy View Post
Out of curiosity, how big of an issue do long time members feel this is?

--jeremy
I don't think it's worth worrying about
 
Old 02-09-2011, 10:39 AM   #12
druuna
LQ Veteran
 
Registered: Sep 2003
Posts: 10,532
Blog Entries: 7

Rep: Reputation: 2374Reputation: 2374Reputation: 2374Reputation: 2374Reputation: 2374Reputation: 2374Reputation: 2374Reputation: 2374Reputation: 2374Reputation: 2374Reputation: 2374
Hi,
Quote:
Originally Posted by jeremy View Post
Out of curiosity, how big of an issue do long time members feel this is?
I find it annoying.... But there are some very legitimate reasons to resurrect an old thread, which makes auto-closure a none issue in my opinion.

A few measures to address this are already in place, but I would be in favour of a tag. Maybe not automatically after a thread is X months/years old, but when someone does resurrect an old thread this tag is added.

Maybe an extra warning to the poster with the option to still abort after s/he pushes the Submit button.

As always, just my 2c.

Last edited by druuna; 02-09-2011 at 10:40 AM.
 
Old 02-09-2011, 10:53 AM   #13
GazL
Senior Member
 
Registered: May 2008
Posts: 3,502

Original Poster
Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024
It's not a huge problem, just an occasional annoyance. If there's a quick win to be had here then IMO it'd be worth the effort. If it's going to take significant engineering then it's an issue we can live with.
 
Old 02-09-2011, 01:28 PM   #14
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by jeremy View Post
Out of curiosity, how big of an issue do long time members feel this is?

--jeremy

The kind of updating that Anisha is talking about is probably a good thing since Google never forgets. However, I see a fair number of ancient threads being pulled up by someone with a question. If the members have moved on, nobody may ever really see the question and all the goodies built into LQ to help people asking questions don't come into play.

Maybe there is a way to add an extra step to old threads and ask the user if they are going to update the info or ask a question. If they're asking a question, maybe bump them to a new thread.
 
Old 02-09-2011, 01:32 PM   #15
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 10,623

Rep: Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657Reputation: 2657
Quote:
Originally Posted by Hangdog42 View Post
Maybe there is a way to add an extra step to old threads and ask the user if they are going to update the info or ask a question. If they're asking a question, maybe bump them to a new thread.
Once again, we already do this. For older threads the Quick Reply is completely disabled. If someone does click the reply button there is a large red "Please note that this thread has not been replied to in over 6 months. Please ensure your reply is still relevant and timely." note at the top.

--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
python thread safety: printing from thread to redirected stdout - safe? BrianK Programming 2 10-11-2010 12:28 PM
LXer: Trinity KDE: KDE 3 Zombified or Resurrected? LXer Syndicated Linux News 0 06-30-2010 08:12 PM
difference b/w AF_ prefix and PF_ prefix related to socket Ashok_mittal Linux - Newbie 1 03-20-2008 05:15 PM
LXer: Linux Fund Visa card resurrected with a new backer LXer Syndicated Linux News 0 07-27-2007 04:46 AM
LRs Resurrected Tuvok Linux From Scratch 0 11-29-2003 11:11 PM


All times are GMT -5. The time now is 04:03 PM.

Main Menu
Advertisement
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