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

    • Flameshot 14.0 Final by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 release notes: This release brings major improvements to multi-monitor support, fractional scaling support, new capture workflows, and a long list of bug fixes across all platforms. Changelog: New Multi-Monitor Capture Workflow New monitor selection screen before capture for better multi-monitor and mixed-scaling support. Option to auto-capture the monitor under the cursor (X11 & Windows). Tray menu can directly select a monitor. Linux Improvements XDG Desktop Portal is now the primary screenshot method. Added legacy X11 fallback option for minimal window managers. New D-Bus capture API for scripting and automation. Windows Enhancements Global screenshot hotkeys now supported (not limited to Print Screen). New portable mode stores settings next to the executable. Clipboard now always uses PNG format for better compatibility. CLI & Platform Updates Redesigned flameshot screen command with per-monitor capture support. Added native Nix Flake support. More compact launcher UI and improved update notifications. Major Fixes Multiple Wayland stability fixes, including KDE Plasma crash fixes. Clipboard compatibility improvements for GNOME, Wayland, X11, Windows, and macOS. Fixed D-Bus hangs, capture crashes, and HiDPI region issues. Other Changes Dropped Ubuntu 20.04 (Focal) support. Updated translations and build infrastructure. Intel macOS builds are no longer provided. [full release notes] Download: Flameshot 14.0 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Helium Browser 0.13.4.1 by Razvan Serea Helium is a private, fast, and honest Chromium-based web browser — built for people, with love. It offers the best privacy by default, unbiased ad-blocking, and a clean experience free from bloat and noise. Proudly based on Ungoogled-Chromium, Helium removes Google’s clutter while keeping a fast, efficient development pipeline. With thoughtful touches like native !bangs and split view, Helium is a people-first, fully open-source browser that puts control back in your hands. Privacy, security, and control come first. Ads, trackers, and third-party cookies are blocked automatically, HTTPS is enforced everywhere, and all Chromium extensions work seamlessly — while Google can’t track your activity. Helium’s 13,000+ offline-ready !bangs let you jump straight to sites or AI tools like ChatGPT instantly. Open-source, people-first, and unbiased, Helium delivers a browsing experience that’s fast, secure, and free from noise, ads, and compromises. Helium Browser key features: Performance Fast, efficient, and lightweight — built on Chromium’s optimized engine. Energy-saving and consistent — stays fast over time without slowing down. No bloat — stripped of unnecessary components for maximum speed. Minimalist interface — compact, clean, and distraction-free. Customizable toolbar — hide elements you don’t need. Smooth and stable — no flicker, lag, or animation glitches. Comfort-focused experience — intuitive and unobtrusive. Privacy & Security Best privacy by default — blocks ads, trackers, phishing, and third-party cookies. Unbiased ad-blocking — powered by community filters and uBlock Origin. No telemetry or analytics — zero background web requests on first launch. Strict HTTPS enforcement — warns for insecure sites. Passkeys supported — modern authentication made simple. No built-in password manager or cloud sync — your data stays yours. Extension Compatibility Full Chromium extension support — including MV2 extensions. Anonymized Chrome Web Store requests — Google can’t track extension installs. Extended MV2 support — maintained for as long as possible. Smart Features Native !bangs — browse faster using 13,000+ offline-ready shortcuts. AI integration — use !chatgpt and others directly from the address bar. Offline functionality — bangs work without an Internet connection. Philosophy People-first design — open source, transparent, and community-driven. No ads, no noise, no bias — privacy and honesty over profit. Helium Browser 0.13.4.1 changelog: 0a4f1149 revision: bump to 4 (#1969) 4848de1f helium/core: enable the chromium screenshot feature (#1968) e0dec3f5 onboarding: integrate strings to i18n system (#1948) 417fa5bc i18n: fix newline parsing for onboarding 7a339b39 i18n: add foraged translations for onboarding 4f090cff i18n/generate: add handling for onboarding strings bfe48d58 i18n_apply: manually override parent grd logic for onboarding strings ab214e3c onboarding: bump in deps, wire up grdp afa6a059 helium/core: disable pdf infobar feature (#1965) eba585e7 helium/ui/vertical: fix new tab button alignment and icon size (#1964) 6ecfc9e0 helium/ui/tabs: fix horizontal tab hover background color (#1963) 3db87dc0 helium/ui/tabs: fix new tab button hover/press colors (#1962) 6bbdcc3e helium/ui: improve tab group UI in all layouts (#1961) 53deb314 helium/ui/tabs: enable tab group hover cards e93aece7 helium/ui/vertical: fix tab group appearance, prevent line overlap 629f5495 helium/ui/tabs: restore solid group header colors, enable new colors 961c962e helium/ui/tabs: move horiz tab group underline to bottom, make it thick c96deab6 merge: update to chromium 149.0.7827.155 (#1959) 36db56b4 i18n: update source.gen.json 5ce006ae patches: refresh for chromium 149.0.7827.155 b4c1ea62 merge: update ungoogled-chromium to 149.0.7827.155 4e5e8671 Update to Chromium 149.0.7827.155 08a3e7da helium/ui/layout: disable mute on collapsed vertical tabs (#1778) a0a5bbaf helium/core: simplify context menu and prevent huge widths (#1951) c4732aac devutils/i18n: add forage command (#1944) 11d16986 devutils/i18n: add an option to translate using local CLI tools (#1942) d820c3a2 i18n/prompt: tighten translation rules to prevent common errors (#1940) cf827007 Update to Chromium 149.0.7827.114 6e3d5164 Update to Chromium 149.0.7827.102 Download: Helium 64-bit | Portable 64-bit |~100.0 MB (Open Source) Download: Helium ARM64 | Portable ARM64 Links: Helium Home Page | macOS | Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • 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
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      579
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      74
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!