Marek Vavruša

Hi, the endpoint supports either `application/dns-message` (RFC8484) and `application/dns-udpwireformat` (older drafts for backwards compatibility). Other formats such as JSON are provided over the same RFC8484 endpoint (`/dns-query`) with different media...

Hi @cookiengineer ! Cloudflare DNS follows Google's DNS over HTTPS JSON interface as per https://developers.cloudflare.com/1.1.1.1/dns-over-https/json-format so that it's at least interoperable until the format is standardized.

I'm in favour of this. I'm running DNS authoritatives and resolvers inside containers, and I'm sure many others do. This prevents me doing that instead of resorting to port redirections....

Another thing that's tricky is `MasterRecordData -> MasterRecordData`. Not sure if there's a better solution for this than Compose into OO::Builder + Parse?

Is this being worked on? I rebased in my branch and added a few more things, and it works okay. I could lend a hand if needed.

Here it is in case you'd like to cherry pick the commits: https://github.com/vavrusa/rust-zipkin/tree/http_reporter

Yes, but that's a different semantics (retrieving new streams). I was thinking about retrieving "activity" on established streams.

It will probably be okay, but I didn't feel confident burying `.unwrap()` in a fundamental library for just a slightly easier use (this is also not something that will be...

Just to clarify - the "👍" means "it's ok to keep it as it is", "please change it to `From`", or "undecided" ?

Hey 👋, I'll update the bindings when I have a moment. It's not as simple as bumping the version number, as ABI has changed and functions now don't exist.