Site suggestion: Auto-close threads older than 6 months.


Recommended Posts

There are an over-whelming number of threads being bumped lately that are older than 4 months old.

Just recently I saw a thread that was 2 years old be bumped, and I just reported a thread that was a year old that got bumped today.

This is kind of ridiculous.

Surely there is some kind of hack for the board that we can have threads that are older than some time frame .. say half a year, be closed?..

It'd make things very nice and tidy on the site, and keep threads that are ancient from resurfacing and having mods having to re-lock them after they're re-reported... for whatever the reason, spam or whatever..

Anyone else think this is a good idea?

Not sure if there are stored procedures in the database we have but if we do then, just pick a base SP, modify it and add a code to retrieve IDs of the threads where there is no activity for past 6 months and lock them. Probably not that hard to do but I am speaking with SQL Server experience in mind. Also and again, I am not sure how the forum sub system is designed so can't gurantee it.

No don't. there can be times when something may need to be brought up again, especially in the music and media sections, and some help sections. Also, some replies to old threads make for great laughs when everyone realizes how old they are :) hehe

Out of curiosity, why is there such hatred of old thread getting bump? I mean if someone have something that they want to contribute .... just let them, rather than create a whole new thread.

Usually, spammers hit old threads instead of new ones.

I think something like this will have more disadvantages than advantages.

Tons of locked threads look messy in the forumbits, for one.

How so?

If it's over 4 months old, it's more than likely .. off the view of the forum zone... anyway.. :blink:

Out of curiosity, why is there such hatred of old thread getting bump? I mean if someone have something that they want to contribute .... just let them, rather than create a whole new thread.

It is not so much as hatred as I would say more or less the practice is "Frowned" upon...The problem is in most cases the person already has found a solution.

Well like for example--

I don't want to have to find the thread because it has been locked- these two happened recently.

The thread went something like this.

The question was -- Is there a way to display a Pdf file inside a Flash container?

8 responses-- then no activity- (the thread was from 2007)
Then all of a sudden 3 years later someone posted something then 2 people posted responses to it until a Moderator realized the person got their answer 3 years ago and closed the thread.

Or a similar post where someone was having issues with Longhorn-- and it was brought back up- 

It would be much simple if someone wishes to post about an old thread and add new content-- Start a new thread-- with a brief summary and a link to the locked (old thread)--

And if lots of people respond back and it becomes current topic-- would be easy for a mod to unlock the original thread and merge the two.

Though I can see a point -- when do threads really become old? 6 months-- Some TV shows have 6 month breaks (so posts like that should not be locked) not to mention other posts such as the first Neowin Post- The "Original Thread" should not be locked since most people eventually make their way their and post to it. (yes I have even done so).

So there are points and counter points about about Auto-Close threads- the question actually would be -- When does a thread become old?

It is not so much as hatred as I would say more or less the practice is "Frowned" upon...The problem is in most cases the person already has found a solution.

Well like for example--

I don't want to have to find the thread because it has been locked- these two happened recently.

The thread went something like this.

The question was -- Is there a way to display a Pdf file inside a Flash container?

8 responses-- then no activity- (the thread was from 2007)
Then all of a sudden 3 years later someone posted something then 2 people posted responses to it until a Moderator realized the person got their answer 3 years ago and closed the thread.

Or a similar post where someone was having issues with Longhorn-- and it was brought back up- 

It would be much simple if someone wishes to post about an old thread and add new content-- Start a new thread-- with a brief summary and a link to the locked (old thread)--

And if lots of people respond back and it becomes current topic-- would be easy for a mod to unlock the original thread and merge the two.

Though I can see a point -- when do threads really become old? 6 months-- Some TV shows have 6 month breaks (so posts like that should not be locked) not to mention other posts such as the first Neowin Post- The "Original Thread" should not be locked since most people eventually make their way their and post to it. (yes I have even done so).

So there are points and counter points about about Auto-Close threads- the question actually would be -- When does a thread become old?

So here's the solution:

For members only visible areas make thread zones have no-expiration date, but for areas that are see-able to guests, make the threads have a cut off timer.

That way it looks like we have a clean board.

If it's a member area, it'll likely be posted in.

If it's accessible and see-able to guests.... it's likely they'll want to join and post in it no matter how old it is without noticing how old the thread is in the first place.

Easy solution.

There are some sections (particularly for hardware and software) where this DOES make sense given that any of the previous responses or solutions is likely out of date.

Or if the solution has already been found...

I see no reason to.

It has no doubt been discussed in the past plenty of times, and is probably brought up now and then like now, In all my time here I have never seen anything similar implemented and no reason to in the end, what is wrong with bumping odl threads if it is relevant in the end?

Sounds like in the end it would be more effort than it is worth.

You asked this last year too, my response is still the same as it was then:

What if someone googles an issue they have a question on, finds a thread from say, 2005, and needs to ask a question regarding it.

It's more steps involved to have them create a new thread, explain the issue, and go from there, rather than just being able to bump an old thread with the needed question. Some won't even bother, and will go elsewhere for a solution.

There is nothing wrong with bumping old threads, providing something relevant is posted.

Mod's can use their judgement accordingly, and if the issue isn't releveant, the post can be deleted, and the thread sent back to the dead.

https://www.neowin.net/forum/topic/856610-suggestion-threads-older-than-2-months-auto-lock-themselves/page__p__592006206entry592006206

You asked this last year too, my response is still the same as it was then:

http://www.neowin.ne...#entry592006206

Wouldn't creating a new thread encourage the reader/user to .. register, which is ultimately, what we want?

Wouldn't creating a new thread encourage the reader/user to .. register, which is ultimately, what we want?

No. They still need to register just to reply, so it doesn't change anything.

Most of the time, when a user bumps an old thread, it's because they don't realize how old the thread is. I don't think the staff will ever implement an auto-locking feature. Instead, perhaps just add a simple notification to alert the user of how old the thread is. Something unobtrusive but it stands out so that the user will notice it before adding a reply. Then the user can decide either to bump the thread or start a new topic.

The last post in this thread is over 3 years old.

Well.. is there a way how to 100% lock it if it's older than a few months unless you're an established member of the community (say older than the thread creation date?).. ?

It's probably doable with SQL (which I think this forum does use. Also I've been here since, 02-June 04 an account this old could probably easily access most of the threads that have been created in the last 3 - 5ish years.

Out of curiosity, why is there such hatred of old thread getting bump? I mean if someone have something that they want to contribute .... just let them, rather than create a whole new thread.

I recently bumped a 2/3 years old news piece to post an update. Nothing wrong with that.

The thing is, a discussion may halt for a prolonged period of time before resuming. This sometimes happens with "official" threads in the Gamers' Hangout forum. Other times, a thread may have to be updated (as is the case with some threads in the Media Room). Keep in mind those are just two examples. There are other scenarios where bumping an old thread is justifiable.

All in all, it's easier for a staff member to use their judgement and close a thread rather than having threads auto-close.

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

    • No registered users viewing this page.
  • Posts

    • Owing to the nature of Windows feature enablement updates, it was distributed over Windows Update services as a complete system upgrade rather than as an ordinary cumulative update
    • Microsoft confirms Windows 11 26H2, urges IT admins to prepare for release by Usama Jawad Windows 11 typically follows an annual update cycle, but Microsoft recently broke that tradition a bit by releasing a "26H1" version in the first half of this year as a "scoped" build for select new silicon PCs only. This version was not available for customers using 24H2 and 25H2 builds, as Microsoft is busy preparing version 26H2 for them, confirmed officially for the first time. In a Windows IT Pro blog, Microsoft has urged IT admins to prepare for the upcoming release of Windows 11 version 26H2. The company has confirmed that this will be a small enablement package (eKB) that will simply light up certain disabled features that are already present in the operating system's code base. This means that the "refined" Windows update and deployment experience will be simpler and quicker, with minimal disruptions, as the feature update will simply toggle a few flags rather than performing a complete replacement. Microsoft has explained that this is all possible because the standard Windows 11 releases share the same servicing branch and hence, the same source code. However, this also means that Windows 11 26H1 users won't be able to upgrade to 26H2 as that is a different branch, but this is something we have known for a while now. Similar to previous annual feature updates, Windows 11 26H2 will offer the following support cycles: 24 months of support for Home, Pro, Pro EDU, and Pro for Workstations editions 36 months of support for Enterprise, Education, IoT Enterprise, and Enterprise Multi-session editions Microsoft has not confirmed a concrete release date for Windows 11 26H2, but noted that it is "coming soon". If we go by the ongoing release cadence, we can expect it to begin rolling out in early October 2026. As such, IT admins have been encouraged to begin validating Windows Insider releases in the Experimental Channel, plan rollout rings, and strategize the utilization of their existing deployment tools.
    • Windows 11 gets new audio improvements in the latest builds by Taras Buria Today's Experimental builds (26H1 and Future Platforms, formerly Canary) pack several audio-related improvements. If your device is enrolled in the Experimental Channel (26H1), you can download build 28120.2315, while those in the Future Platforms version have build 29613.1000 to try. Here is what is new in build 29613.1000: [Audio] Following up on our previous improvements, we’re making some more adjustments to Settings > System > Sounds based on your feedback. Namely, we’ve updated the “All sound devices” page so: You now have the ability to change default devices from this page. Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. We’ve adjusted the page design slightly so now you can filter whether you’re viewing input or output devices. We’ve added toggles so you can choose if you want to hide or show disabled, disconnected, and unplugged devices on this page. We’ve also updated the input and output audio properties page for devices in Settings to now include jack information for those that need it. And here is the changelog for build 28120.2315: This update includes a small number of minor bug fixes and improvements. [Accessibility] This update improves caption style responsiveness by redrawing captions immediately for caption style changes. If no current caption is visible, a sample caption string is displayed. [Audio] This update improves the reliability of the inbox HD Audio driver. You can find the official release notes for build 28120.2315 here and for build 29613.1000 here.
    • I agree with what I think you are saying, just not in the way you are saying it. Like any tool, the amount it represents your work is perorational to the effort you put into it. It is similar to why 2nd grade math students learning to add and subtract are not allowed to use calculators, but a high-school calculous student is. For the 2nd grader, that tool would completely replace the work they are doing, for the calculous student the same tool allows them to work far more effectively while in no way replacing their effort or knowable. If you spend 30 seconds writing a prompt, then the image that comes out is no more "yours" than if you found the same image with a Google Image search. However, many of these generative tools also support highly iterative processes that allow back and forth, and merging generated images with photos or human created images. I am sure you would agree that a human spending hours of time working on a project, even if AI was involved in the process, still reflects that human's work.
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      575
    2. 2
      +Edouard
      189
    3. 3
      Michael Scrip
      79
    4. 4
      PsYcHoKiLLa
      78
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!