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

    • Samsung Galaxy Watch8 is now selling at its lowest price ever by Fiza Ali Amazon is now offering Samsung Galaxy Watch8 at its lowest price yet with a 34% discount (purchase link down below). The Galaxy Watch8 is equipped with a 1.5-inch Super AMOLED display with a resolution of 480x480 pixels and support for 16 million colours. The watch is powered by a penta-core processor with clock speeds of up to 1.6GHz, runs Wear OS, and includes 2GB of RAM and 32GB of internal storage. For connectivity, the watch supports Bluetooth 5.3, Wi-Fi 802.11a/b/g/n on both 2.4GHz and 5GHz bands, and NFC. Furthermore, supported Bluetooth profiles include A2DP, AVRCP, HFP, and HSP. Location services are provided through GPS, GLONASS, BeiDou, and Galileo satellite systems. Moreover, the Galaxy Watch8 includes a range of sensors as well, including an accelerometer, barometer, bioelectrical impedance analysis (BIA) sensor, electrical heart sensor (ECG), optical heart rate sensor, gyroscope, geomagnetic sensor, infrared temperature sensor, and ambient light sensor. For media playback, the watch supports MP3, M4A, 3GA, AAC, OGG, OGA, WAV, AMR, and AWB audio formats. In terms of water resistance, it has a 5 ATM rating, which should make it suitable for swimming and everyday exposure to water. Finally, the device is powered by a 435mAh lithium-ion battery, and when it comes to its performance, Samsung rates the battery for up to 40 hours of use with the Always-On Display turned off. Samsung Galaxy Watch 8 (2025) 44mm Smartwatch: $249.99 (Amazon US) - 34% off Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Remarkably based article from Garter - apparently there IS someone working there that actually understands mainframe systems.
  • Recent Achievements

    • 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
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      591
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      73
    4. 4
      Michael Scrip
      65
    5. 5
      ATLien_0
      64
  • Tell a friend

    Love Neowin? Tell a friend!