varx/tech on Nostr: nprofile1q…rk39d I mean, the CBOR spec also has explicit instructions on how to ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq8369m6ejyjfh47ths7qrlvqcu8jvyzxnuysx72cpvg95jfvt9l0sgrk39d (nprofile…k39d) I mean, the CBOR spec also has explicit instructions on how to handle map keys in canonical mode, but kotlinx.serialization's implementation just... doesn't do that. :-/
It might be that other formats would help avoid this issue, but I think ultimately the best measure of prevention is going to be a set of protocol test vectors—"your application must parse these files in this way, and completely fail to parse these other files".
It might be that other formats would help avoid this issue, but I think ultimately the best measure of prevention is going to be a set of protocol test vectors—"your application must parse these files in this way, and completely fail to parse these other files".