I don’t think “necroposting” is something inherently bad[0], but specifically insisting (or expecting) that open-source project maintainer remembers a 100-scree

I don’t think “necroposting” is something inherently bad[0], but specifically insisting (or expecting) that open-source project maintainer remembers a 100-screen thread every time anyone wants to bring it up is IMO ill-mannered. A random person online invests an afternoon to read through a years old issue thread and decides to comment, expecting the maintainer to reply. Meanwhile, maintainer has dozens of such issues, and dozens of frustrated users bringing up each of them every week. Asking the submitter to respect a previously made maintainer’s decision, file a new issue and invest their own time to concisely summarize the status quo seems only fair. In other words, diverting discussion to a new thread is a chance to compress old context into a short summary, like you would squash a Git history—except in this case the old closed issue thread is fully linkable and isn’t going anywhere. [0] That said, it depends on maintainer’s personality. I can see how some could feel losing control and demoralised by ever-evolving difficult-to-track discussions on previously closed issues.