For all my frens trapped in clients that don't respect long-form.

https://njump.me/naddr1qvzqqqr4gupzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpr3mhxue69uhhg6r9vd5hgctyv4kzumn0wd68yvfwvdhk6tcqp5cnwv35x5urzd34xs6ngvq5mcewx

quoting
naddr1qq…umwg

The user is never wrong

Here are some non-suspect ways a dev team can respond to a bug report

1. Thank you for reporting. We already opened issue ABC123 to track that and you can follow the progress on our issues board.

2. Oh, wow! That’s an odd behavior. 🤔 Can you give me more information about your setup and the precise steps you took to find that, so that we can track down the cause?

3. Yeah, that’s a known flaw, I’m afraid. We’ve got this workaround available…

4. Oh, that’s actually a path/use-case/feature we hadn’t considered, yet. I’ll discuss it with the team and get back to you, concerning the possible implementation.

Sus ways a dev team can respond to a bug report

1. User error.

2. No one else has reported that.

3. Do I look like I have all day to deal with your whining? The road map. Read it.

4. 🦗🦗🦗🦗