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

    • Codec Tweak Tool 6.7.7 by Razvan Serea This tool is a Swiss army knife for managing codecs and codec settings. Codec Tweak Tool will scan for broken filters and remove them. If the tool detects something that is broken, it will then prompt you with the details and you will be given the option to remove the broken item. Generate a detailed log of all installed codecs and filters, enable/disable more than 250 popular codecs and filters (if they are installed), manage preferred source filters, and reset settings. With this tool you can do things like: Scan the registry to detect and remove broken references to codecs and filters. Enable/disable more than 200 popular codecs and filters (if they are installed). Manage preferred source filters (a.k.a. splitters). Detect broken codecs and DirectShow filters. Fix problems with the standard DirectShow filters of Windows. A fix for a specific sound problem. Generate a text file with detailed information about all installed codecs and DirectShow filters, along with other relevant system information. Reset settings to recommended values for many popular codecs and DirectShow filters. Configure audio output settings for several popular audio decoders. Several configuration options for a few DirectShow filters that don't have an easily accessible interface for those options. Easy access to the configuration interfaces of various codecs and DirectShow filters Backup the settings of several codecs and DirectShow filters. Replace your current settings with those from a previous backup. Manage DirectShow filters - Enable or disable DirectShow filters. Manage ACM/VFW codecs - Enable or disable ACM/VFW codecs. Enable or disable DirectX Media Objects. Configure your preferred DirectShow source filters (a.k.a. splitters) for several common file extensions. Enable or disable the generation of thumbnails for several common video file formats in Windows Explorer. Download: Codec Tweak Tool 6.7.7 | 1.5 MB (Freeware) View: Codec Tweak Tool Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The site is pretty sparse on features / tech specs. Can I plug it into a PC/hone/Switch via USB-C and use it as an external display? If so, what's the virtual resolution of the screen, the refresh rate, PPI of the image etc? Is the text crisp enough to use for coding at say 12pt? Is it good enough for playing dark games, like say Path of Exile 2? How about fast games like car racing games? Just how do they expect anyone to order this thing without giving out all this info?
    • I call complete bs on this - no way your average joe / jane is using AI.
  • 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
      546
    2. 2
      +Edouard
      159
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      neufuse
      65
    5. 5
      Steven P.
      65
  • Tell a friend

    Love Neowin? Tell a friend!