you see, there is a problem, i don't like cbor after dealing with it in my work with bluesky so why do you love it so much? why do you prefer it compared to msgpack or protobuf or flatbuffers or capnproto? keep in mind this needs to connect together apps written in go, rust, javascript, java, c, c++ and maybe at least reasonable support for python and c# from what i've seen, and it's been a while since i've looked that close, protobuf was the most well and fully-supported across all of these languages personally, i would want to use flatbuffers, and currently the Go version of this protocol encoding is shitty, but i could imagine myself reworking it in a month or two into something that is really natural to use with Go, because i have already in fact written an on-demand protocol buffer encoder, twice, in fact, simple TLV thing that was based on ad-hoc dynamic interface array message descriptors