-
@ Laeserin
2024-08-25 10:41:04
# 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](nostr:naddr1qq9yzmr90pskuerjd9sszrthwden5te0dehhxtnvdakqyg8ayz8w3j8jsduq492j39hysg7vnhrtl4zzqcugj4m3q62qlkf8cypsgqqqw7vszahgpn).
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) 🦗🦗🦗🦗