| 20 Mar 2026 |
| *  piegames sighs | 10:33:59 |
| piegames | I hate JSON so fucking much | 10:34:03 |
| piegames | currently reading the I-JSON spec and got painfully reminded that JSON has zero non-text handling capabilities | 10:34:37 |
 Sergei Zimmerman (xokdvium) | I recall there seemed to be some AWS endpoint that legitimately used duplicate keys too | 10:34:41 |
| Sergei Zimmerman (xokdvium) | Though I’m not sure I can find the reference now | 10:35:15 |
| piegames | let me rephrase the question, are there any reasonable use cases for duplicate keys where parsing both and then using only one of the values is the correct behavior? | 10:36:19 |
 emily | it's sorta like asking if there's any use case for parsing web pages with invalid HTML the same way everyone else parses them | 10:37:24 |
| emily | the use case is you can browse the web like everyone else | 10:37:36 |
| emily | the documents are dodgy from an interoperability/sanity standpoint, but when they exist in the wild and everyone treats them the same way in practice… | 10:37:55 |
 Qyriad | Unfortunately retaining only one of the values is arguably a more compatible behavior because the alternative is e.g. parsing them into a list, which is an entirely different type | 10:38:10 |
