# Should old threads be auto-locked (more aggressively)? **URL:** \ **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:** 1\ **Showing post:** 24
**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")
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… --- _[View the full topic](https://discuss.python.org/t/should-old-threads-be-auto-locked-more-aggressively/42557)._