[suggestion] Warn on resurrection


Recommended Posts

With the repeated (though not always very frequent) post that resurrects a very old thread, might it be possible to include a bit of code that would alert a user when they post a new comment in a thread that has been idle for 6 months or older?

Basically, pop open something that makes them realize the thread may have exceeded its shelf life, and give them the option to cancel the post, or make it a new thread, if they think it contains appropriately new information. Because every time someone resurrects a thread, you get about 4 more posts complaining about the resurrection.

Link to comment
Share on other sites

This would be a nice idea if it could be implemented! I just told someone that he/she had resurrected a year old thread! I did not whinge at the person in any way, all I did was let them know!

Link to comment
Share on other sites

Or maybe people should stop whining?

If someone has interest in an old thread, or wants to follow-up on a solution, do they really care that the thread has been idle?

Link to comment
Share on other sites

Gotta admit, there have been several times where I just refrained from making a post altogether, because if I made a new post on a certain topic I knew I'd get multiple follow-up posts asking me if I ever heard of the search function, and if I added a comment on an older existing thread I new I'd get multiple follow-up posts asking why I resurrected an old thread... :p

Link to comment
Share on other sites

Gotta admit, there have been several times where I just refrained from making a post altogether, because if I made a new post on a certain topic I knew I'd get multiple follow-up posts asking me if I ever heard of the search function, and if I added a comment on an older existing thread I new I'd get multiple follow-up posts asking why I resurrected an old thread... :p

I agree, the situation really is a catch-22. I guess it just needs to be moderated, and only penalized under certain circumstances. Some threads make sense to resurrect, but others are just lame.

Link to comment
Share on other sites

I agree, the situation really is a catch-22. I guess it just needs to be moderated, and only penalized under certain circumstances. Some threads make sense to resurrect, but others are just lame.

My point was that some people found a thread during a search, didn't pay attention to the date, and post something like "I had that happen, too" or some such - not realizing it isn't a current discussion.

The alert would just let them know and give them a chance to not resurrect the thread (against rule 10) or post if they feel they have a good update, or create a new thread if their information is significantly different then the OP.

After all, we could have one big BSOD thread, constantly bumped and updated as new people find they have a BSOD. But that wouldn't make sense to do.

Link to comment
Share on other sites

Or maybe people should stop whining?

If someone has interest in an old thread, or wants to follow-up on a solution, do they really care that the thread has been idle?

Followup is fine, provided they didn't just answer a 6 year-old question with a magical step that everyone's known about for the last 5 years.

Link to comment
Share on other sites

agreed it should depend on the topic. although would it be wrong to bump.gif and old game off the off topic section. for getting a forum game going again?

Link to comment
Share on other sites

I agree with the idea, but that sounds like a lot of work for something that doesn't happen all too often. In that case, a moderator will usually close the thread in these cases.

Link to comment
Share on other sites

My only complaint is whatever you do some people are never happy.

If someone resurrects a +6mth old thread then people complain.

If someone starts a new thread that has been covered +6mths ago then someone complains they didn't search.

I say warn all those who complain.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.