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

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      596
    2. 2
      +Edouard
      188
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!