# Should old threads be auto-locked (more aggressively)?

**URL:** <https://discuss.python.org/t/should-old-threads-be-auto-locked-more-aggressively/42557>\
**Category:** Discourse Feedback\
**Created:** [January 5, 2024, 6:38pm UTC](https://discuss.python.org/t/should-old-threads-be-auto-locked-more-aggressively/42557 "2024-01-05T18:38:04Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Flimm](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/flimm/32/16046_2.png) [@Flimm](https://discuss.python.org/u/Flimm)\
**Post date:** [January 12, 2024, 1:50pm UTC](https://discuss.python.org/t/should-old-threads-be-auto-locked-more-aggressively/42557/21 "2024-01-12T13:50:42Z")

</div>

If the information is so out of date that we need to lock it, can we also delete it, or at least hide it from search engines? It’s frustrating to be directed to information that is out of date and locked.

Conversely, if the information is still useful enough to keep available, then it should stay open for further discussion, IMHO. It’s frustrating to be restricted from updating or commenting on information that needs updating.

---

<div class="post-metadata">

**Author:** ![jamestwebber](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jamestwebber/32/12799_2.png) [@jamestwebber](https://discuss.python.org/u/jamestwebber)\
**Post date:** [January 12, 2024, 2:28pm UTC](https://discuss.python.org/t/should-old-threads-be-auto-locked-more-aggressively/42557/22 "2024-01-12T14:28:59Z")

</div>

I don’t think anything should get deleted. But threads aren’t just information that can go out of date, they contain ideas and discussions that might have naturally concluded amomg the participants. I find it jarring (and typically not useful) for a new person to join such a discussion many months later.

Maybe this is just personal preference and I should mute things more. But if lots of people were experiencing the same thing then maybe there’s a more global tweak that could help. I don’t think the conversation here indicates that, though.

---

<div class="post-metadata">

**Author:** ![bryevdv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/bryevdv/32/7424_2.png) [@bryevdv](https://discuss.python.org/u/bryevdv)\
**Post date:** [January 12, 2024, 6:18pm UTC](https://discuss.python.org/t/should-old-threads-be-auto-locked-more-aggressively/42557/23 "2024-01-12T18:18:48Z")

</div>

I admin another discourse for an open source project and we auto-lock after three months. It is absolutely an increased burden on folks who are already donating their time for free, to have to sort through some necro-thread to determine what is or isn’t relevant to some new post three years later. Respect contributors time and just open a new thread, with all relevant, current details in one place, linking to anything older if it’s truly important.

---

<div class="post-metadata">

**Author:** ![CAM-Gerlach](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/cam-gerlach/32/3688_2.png) [@CAM-Gerlach](https://discuss.python.org/u/CAM-Gerlach)\
**Post date:** [January 24, 2024, 5:08pm UTC](https://discuss.python.org/t/should-old-threads-be-auto-locked-more-aggressively/42557/24 "2024-01-24T17:08:22Z")

</div>

To note, much of the same motivation seems to be behind t[his thread](https://discuss.python.org/t/should-existing-threads-be-used-for-new-tech-support-problems/44025), and the suggestions and opinions here inform our response, so I encourage those interested here to share their thoughts to this as well:

> [@Should existing threads be used for new tech-support problems?](https://discuss.python.org/t/should-existing-threads-be-used-for-new-tech-support-problems/44025):
>
> Recently I’ve noticed a few cases where someone needed help with setting up or installing something (whether Python itself, Pip, a third-party package…) - but instead of making a new thread, they posted in an existing thread that appears to be about the same or a similar problem, but experienced by someone else with perhaps a completely different environment/diagnostics. Typically this happens a long time after the original case is resolved (or abandoned), and at most tangential reference is mad…

[Previous page](https://discuss.python.org/t/should-old-threads-be-auto-locked-more-aggressively/42557.md?page=1)
