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

    • I just looked on my computer and there are settings and log files for utilities I have never even turned on!
    • O&O ShutUp10 3.1.1104 by Razvan Serea O&O ShutUp10 offers a simple yet effective way to take control of your Windows privacy. It provides access to almost 50 privacy-related tweaks, most of them hidden or not easily accessible to the average computer users. Using a very simple interface, you decide how Windows 10/11 should respect your privacy by deciding which unwanted functions should be deactivated. Using ShutUp10 you can easily disable Windows Defender, turn off telemetry, disable peer-to-peer updates, turn off Wi-Fi Sense, disable automatic Windows updates, turn off and reset Cortana and more. ShutUp10 allows you to create a System Restore point before you apply any changes, so that you can revert your system at any time if you run into problems. O&O ShutUp10 is entirely free and does not have to be installed – it can be simply run directly and immediately on your PC. And it will not install or download retrospectively unwanted or unnecessary software, like so many other programs do these days! O&O ShutUp10 Free and Premium The latest version brings O&O ShutUp10 Premium, expanding the app’s long-standing privacy controls with automatic enforcement of user-defined settings. Instead of manually rechecking options after every Windows update, users can set their preferred privacy configuration once—or apply recommended settings in a single click—and the tool continuously monitors them in the background. If Windows 10 or 11 re-enables disabled features or introduces new data collection paths, Premium restores the chosen settings automatically without user intervention. The free version remains available and fully functional for manual adjustments, offering the same core privacy controls for Windows. However, the Premium tier is aimed at users who want long-term, hands-off protection, adding automatic reapplication after updates, ongoing monitoring, and optional notifications to ensure privacy settings remain consistent over time. O&O ShutUp10 3.1.1104 changelog: Added “Show Differences” button in the overview panel “Don’t show again” option for the restore point prompt Ctrl+F keyboard shortcut for search/filter functionality Detection and linking of system-wide and user-specific setting associations Automatic search while typing PREM: Option to preserve notification counters and timestamps across application restarts PREM: Reset blocked settings button in the Settings dialog PREM: Informational message when no settings are blocked PREM: Update check can also be triggered from the menu PREM: Notification deduplication and activity log summary feature Improved L005 “Disable Windows Location Service”: Version-specific split (up to Windows 11 23H2) and new variant for Windows 11 24H2+ L001 (Disable Location): Added Night Light warning to the description in all languages Search now detects setting IDs even when ID display is disabled and offers to enable it Detection and removal of Copilot/AI desktop apps in RecallTerminator Optimized High DPI support PREM: Reset button is now only enabled when blocked items exist – setting IDs are shown in the confirmation dialog PREM: Updated tray icons with higher-resolution versions PREM: Activity Log timestamps now use localized date and time formats PREM: Tray icon status now uses OK/Warning indicators and localized tooltips PREM: Recall folder detection switched to service-based detection PREM: Copilot uninstallation now provides UI feedback and improved verification Fixed Description text was not displayed correctly for the last item and disappeared when clicking the scrollbar Crash when clicking a search result heading or the […] button PREM: Installation path is now correctly preserved during upgrades PREM: Tray icon was not reliably removed when exiting the application PREM: Main window was not displayed correctly in single-instance mode PREM: Incorrect display of the & symbol in tray icon tooltips on Windows 10 PREM: Fixed notification flooding after sleep/standby PREM: Dashboard was not refreshed after applying recommended settings during onboarding PREM: Progress bar was not reset after deleting Recall folders PREM: Fixed service startup failures PREM: Fixed incorrect drift detection when Automatic Protection was disabled PREM: Notifications now correctly count all deviating settings when protection is enabled PREM: Registration Wizard was shown after sleep/standby despite a valid license Download: O&O ShutUp10 3.1.1104 | 76.4 MB (Freeware) Download: O&O ShutUp10 32-bit | ARM64 View: O&O ShutUp10 Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Fascinating...W h i t e P o w e r is now also asterisks out.  
    • In the past few days I have noticed two odd moderation activities. First, when I posted the term 'White Nationist Christian' it was asterisk's out. When I changed it to **** it was allowed! Second, in the Politics is a ###business thread I was allowed to post that the GOP is a party of p e d ophiles but I was censored  when I posted the GOP are a party of p e d ophile protectors. Wtf Neowin. Please explain.
  • Recent Achievements

    • One Month Later
      Vincian earned a badge
      One Month Later
    • First Post
      Jocimo earned a badge
      First Post
    • Week One Done
      suprememobiles48 earned a badge
      Week One Done
    • One Month Later
      Windows Guy earned a badge
      One Month Later
    • One Month Later
      Prasann earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      547
    2. 2
      +Edouard
      166
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Steven P.
      66
    5. 5
      neufuse
      65
  • Tell a friend

    Love Neowin? Tell a friend!