Topic closing

Question

It seems there is an urgent need on the part of mods to close topics. As one example:
https://bbs.archlinux.org/viewtopic.php?id=88018
The post at the bottom of this thread was quite useful to me in pointing out that AGP also had to be built into the kernel.
What is the point of closing this thread?
From my perspective as a user, this action makes me feel like some overlord is censoring inter-user communications (no, not you phrakture 8-)
I would like to point out this aspect of the posting rules (so handily provided through sigline):
https://wiki.archlinux.org/index.php/Forum_Etiquette#Life_is_a_Two-way_Street
One person's (mods) necro-bumping may be another person's (users) valuable piece of debug information.
Perhaps something is old news to a person with >5000 posts, but may still be an open and active topic for someone just starting to try to solve the problem.
Please, try to think about that Two-way_Street rule from the perspective of the traffic going the other way: sometimes an issue comes up for another person months after the initial posting. The issue is still current for the person having it, and sometimes new data comes to light on the same old topic.
Let those necro-bumpers be 8-)
After 30 years in engineering decision making (and 8 years of running arch everyday) I've learned to respect the lazy programmer, i.e.:
Unless there is a compelling reason to take action, the best thing to do is nothing (aka KISS)
I know all the mods work hard and dedicate a huge amount of their personal time to arch.
A sincere THANK YOU to all the mods, devs, TUs and other distro helpers!!!!
Please, remember the lowly user trying to overcome their own little problem that no one else cares about (often under time and learning curve pressure)
Thanks again for everyone's contributions to arch!
android

Answer 1

Thank you both for your replies.
I don't feel like anyone (Inxsible in this case) did anything wrong, or even made
an egregious oversight
I'm just trying to provide a users perspective on what constitutes "necro".
In running arch for as long as I have (forum user id 221) I am totally (and sometimes painfully) aware of the rate of change at arch.
While the release may roll on, I often don't upgrade certain machines for many months, or even years. Depending on the role the machine plays, stability is often way more important than running the very latest upstream.
So when i do upgrade a server, or other intranet appliance, I may face issues that first surfaced months prior. As I deal with it, new data or aspects may come to light that follow in the vein of the old thread.
This is just "my usage model", but given the framework nature of the arch distro, many different users apply it into many different situations. (such as embedded) this gives rise to the fact that there isn't really one "arch way" but really many many different "arch ways".
All I'm saying is: Please have some empathy for those that aren't on the boards or "pacman -Syu"ing every day. We're still arch users and still try to contribute in the ways we are able.
Regarding the "Report function" pointed out above by Inxsible: I guess I had an impression that the "Report" had some negative connotation. In the future I'll use this mechanism before publicly posting.
I used to feel the same way about "Flag as Out of Date" and have come to think it more as a heads up to the maintainer (although some maintainers still get testy when you flag their baby) So I guess this is why I had the negative impression of the "report" function.
I hope I've communicated that I don't really have a complaint, with Inxsible or the forums, I'm just trying to increase sensitivity to some users not being as "with it" in a daily (or monthly) way as the mods and other uber regulars. I can see that a report or PM could have been a better way to discuss this, I'll do better next time.
Thanks again to each of you!
android