Suggestion: Threads older than 2 months, auto-lock themselves.


Recommended Posts

I know that certain forum software has this ability... but I don't know if Neowin's does or not.

I'd like to see it if a thread sits unactive for two months, it automatically locks itself.

Why?

I'm seeing quite a few threads being rebumped up by new faces not paying attention to the date which threads are posted and this would solve a ton of issues.

It'd also stop spam bots from bumping up old threads with spam messages.

There are plenty of legitimate threads that can remain open for longer than two months. Example: a member posts a problem in say Hardware Hangout, and doesn't get any solution. Then a few months later, he discovers a fix. Instead of spawning a new thread, he can simply bump his old thread so other readers can have some backstory to follow.

The status quo's fine. Staffers can attend to any threads they see randomly bumped by spammers.

Your suggestion holds water though for news comments. (and you probably heard that already months ago)

I wouldn't object to that suggestion. Disregarding my opinions, there is probably a legitimate reason for thread auto-locking.

You'll have to ask the devs though, if it's feasible.

There are plenty of legitimate threads that can remain open for longer than two months. Example: a member posts a problem in say Hardware Hangout, and doesn't get any solution. Then a few months later, he discovers a fix. Instead of spawning a new thread, he can simply bump his old thread so other readers can have some backstory to follow.

The status quo's fine. Staffers can attend to any threads they see randomly bumped by spammers.

Your suggestion holds water though for news comments. (and you probably heard that already months ago)

I think you're right. I haven't seen any major issues.

There are plenty of legitimate threads that can remain open for longer than two months. Example: a member posts a problem in say Hardware Hangout, and doesn't get any solution. Then a few months later, he discovers a fix. Instead of spawning a new thread, he can simply bump his old thread so other readers can have some backstory to follow.

The status quo's fine. Staffers can attend to any threads they see randomly bumped by spammers.

Your suggestion holds water though for news comments. (and you probably heard that already months ago)

I think you're right. I haven't seen any major issues.

I personally see this causing more issues then it would solve. Members would need to PM a staff member to open a thread back up, rather than someone on duty to close an old bumped thread.

It doesn't hurt anybody, and yes it is annoying, but no full-proof solution.

I agree with Andrew_Lyle. The current way of closing threads that have been revived is better. It gives the staff member the option of closing it or leaving it open (if it's an official discussion thread, etc).

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.

I think that threads should auto-lock eventually, but two months is way too soon. I think something like 1-2 years is a long enough time to wait before locking a topic.

Most of the time, when an old topic is bumped, I don't notice how old the thread is, and neither do many other users. It causes confusion, and the thread ends up getting locked anyways.

I actually would prefer that the person started a new topic, rather than bumping a thread that's almost five years old:

https://www.neowin.net/forum/index.php?show...#entry592038324

I actually would prefer that the person started a new topic, rather than bumping a thread that's almost five years old:

https://www.neowin.net/forum/index.php?show...#entry592038324

I agree with this. To be honest, for "I have a problem" threads it is almost always more appropriate to start your own topic than try and hijack someone elses (regardless how old it is)

I think that threads should auto-lock eventually, but two months is way too soon. I think something like 1-2 years is a long enough time to wait before locking a topic.

Most of the time, when an old topic is bumped, I don't notice how old the thread is, and neither do many other users. It causes confusion, and the thread ends up getting locked anyways.

I actually would prefer that the person started a new topic, rather than bumping a thread that's almost five years old:

https://www.neowin.net/forum/index.php?show...#entry592038324

And the mods locked that thread within 2 hours of it being bumped. I don't think there is anything wrong with the way it works now. Unless the mods are having issues about locking too many bumped threads I don't see why it would bother the standard users.

I'd like to see it if a thread sits unactive for two months, it automatically locks itself.

Why?

So you want more posts that might be discussing the same topic or problem. You don't want many of those threads full of questions with no solutions or answers coming up on Google searches. You might be digging around google search results only to find 95% of those links lead to unsolved and locked threads. It is best to leave those open so people can post solutions. I had a few problems and they took months to solve. In the end, I posted my solution to the existing post instead of creating another post so anyone who google search would find the question AND the answer in one click.

This is a legit reason why forum runners should never lock old threads, otherwise the forums would only get bigger and messier.

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

    • No registered users viewing this page.
  • Posts

    • Thanks
    • Can confirm, I've built stuff for others and no complaints using their products.
    • Yes I agree, it's annoying. You can now miss tabs unless you point low enough.
    • Sysinternals Suite 2026.17.06 by Razvan Serea The Sysinternals Suite is a comprehensive package of advanced Windows utilities created by Mark Russinovich, who launched the Sysinternals website in 1996 to share his system tools and technical resources. This suite combines a wide range of troubleshooting and diagnostic tools, including Process Explorer, Process Monitor, Sysmon, Autoruns, ProcDump, the PsTools collection, and many others. It provides everything IT professionals and developers need to manage, monitor, and troubleshoot Windows systems and applications. The Suite bundles all of the core troubleshooting utilities along with their help files. Non-troubleshooting extras—such as the BSOD Screen Saver or NotMyFault—are excluded. In addition to the well-known tools, it also includes AccessChk, Autologon, Ctrl2Cap, DiskView, Disk Usage (DU), LogonSessions, PageDefrag, PsLogList, PsPasswd, RegMon, RootkitRevealer, TCPView, VMMap, ZoomIt, and more. Sysinternals Suite 2026.17.06 changelog: Autoruns v14.3 - This update to Autoruns, a utility for monitoring startup items, adds bug fixes and improves the command-line application autorunsc. ZoomIt v12.1 - This update to ZoomIt, a screen magnification and annotation tool, adds image backgrounds, webcam background blur and microphone noise cancellation support. Coreinfo v4.01 - This update to Coreinfo, a tool that reports processor, socket, NUMA memory, and cache topology of a system, as well as processor features supported, adds support for new processor features. DebugView v5.02 - This update to DebugView, a tool for displaying both kernel-mode and Win32 debug output, adds Ctrl-Shift-A support for selecting all output, and agent skills support for the CLI utility. LiveKd v5.64 - This update to LiveKd, a utility that allows running the kernel debugger on a live system, fixes a debugging privileges issue. ProcDump 3.5.2 for Linux - This update to ProcDump for Linux, a tool for capturing process dumps, adds .NET counters and a custom core dumper. Process Monitor v4.04 - This update to Process Monitor, a utility for observing real-time file system, Registry, and process or thread activity, adds some bug fixes Sysmon v15.21 - This update to Sysmon, an advanced host security monitoring tool, adds some bug fixes. Download: Sysinternals Suite 2026.17.06 | 168.0 MB (Freeware) Download: Sysinternals Suite for ARM64 | 15.4 MB Link: Sysinternals Suite Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Given only Volume license customers and specific resellers can obtain the LTSC versions legitimately it seems likely that this has been tinkered with quite a lot!
  • Recent Achievements

    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
    • First Post
      Jocimo earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      542
    2. 2
      +Edouard
      167
    3. 3
      PsYcHoKiLLa
      85
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!