Event JSON
{
"id": "2777ba32ff10c374eef55648f8106821d066b11914cf79cd0373f7142e60e7c0",
"pubkey": "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319",
"created_at": 1724582464,
"kind": 30023,
"tags": [
[
"d",
"1724581654540"
],
[
"title",
"Hello? Yes, customer service speaking."
],
[
"summary",
"Users are people, too."
],
[
"image",
"https://i.nostr.build/4GqlVLUm1pXtXAiU.png"
],
[
"published_at",
"1724582456"
],
[
"alt",
"This is a long form article, you can read it in https://habla.news/a/naddr1qvzqqqr4gupzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqqxnzdejxs6nsvfkx56r2dpsv7d4au"
],
[
"a",
"30617:fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1:Alexandria",
"wss://nos.lol",
"mention"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
]
],
"content": "# The user is never wrong\n\n## Here are some non-suspect ways a dev team can respond to a bug report\n\n1) Thank you for reporting. We already opened issue ABC123 to track that and you can follow the progress on [our issues board](nostr:naddr1qq9yzmr90pskuerjd9sszrthwden5te0dehhxtnvdakqyg8ayz8w3j8jsduq492j39hysg7vnhrtl4zzqcugj4m3q62qlkf8cypsgqqqw7vszahgpn).\n\n2) 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?\n\n3) Yeah, that's a known flaw, I'm afraid. We've got this workaround available...\n\n4) 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.\n\n## Sus ways a dev team can respond to a bug report \n\n1) User error.\n\n2) No one else has reported that.\n\n3) Do I look like I have all day to deal with your whining? The road map. Read it.\n\n4) 🦗🦗🦗🦗",
"sig": "16ecd1b7be8d03e53218e3552fda1206051d3ff786e576ddcef8ddc8742d6b0866f00dca30b450de7510d7b2728ce569f60f882f940e71d3683bf918225f5bee"
}
