In comparison to _paid_ software testing, which doesn't change the point at all: if they were paid to find bugs, they wouldn't be paid for useless and unactionable reports.
>you’re complaining that listening to your users is hard
Sometimes - and I'd wager most of the time - they are, yes, unless your product solely attracts technically competent and advanced users that can attempt to understand/reason about what is causing the issue.
That's entirely the wrong take, IMO.
Listening to users is easy, but the users often don't say anything when they speak. Those non-reports are basically spam that should be automatically thrown away.
I’d always reply though, usually with something equally terse.
As a developer sharing my code online, I don't even know where to begin answering that.
This is typical non-tech spam.
If a user wants to use a piece of software to do A and several different pieces of code do that - why should they choose yours.
What is your selling point.
Especially if they have been using the other product why should they switch to yours?
I'm not making money from it, so trying to convince some random individual to use it is a waste of my time. Sure, I'll describe the features in the README and possibly include comparisons to other software, but I won't go out of my way to convince a specific rando just because they asked.