I'd call that first one "The Hemingway Award For Terminal Concision In Fault Diagnosis"

There's a legitimate reason for posting low information issues - finding out if it's a known limitation or issue (that didn't come up in a search) before putting in extra effort to document something that's already been documented and discussed elsewhere. Maybe not "doesn't work" (two words) exactly, but "This doesn't work for me with the X234 hardware" (... with an implied "is this expected?").

It's very common for people new to projects or with limited technical skills to assume that the problems they face are common/well known or that other people know much more than them.

The frustration responders face is due to the mismatch of assumptions, if the issue is in fact not common or well known, but IMO a simple "I haven't seen that before, please post full diagnostics" is an easy and reasonable boilerplate response.

> "This doesn't work for me with the X234 hardware"

The problem with that phrase is that you didn't state what is not working. I don't expect - although highly welcome - a complete diagnostics from the reporter, but please at least write the steps to reproduce your issue.

Yes. “Install failed with permissions error” or “runs but doesn’t seem to be listening on configured port” at least.

> "The Novelist": Opens an issue or replies to a thread with only the words "doesn't work" with no indication of what they tried, how they know it doesn't work, or any error messages.

"The Shrug Reporter" might be a better name [0]

[0] https://www.computer-dictionary-online.org/definitions-s/shr...