trust-dns VS gnuradio

If you don't know what is Trust-DNS / Hickory DNS, this seems to be the repo: https://github.com/bluejekyll/trust-dns

IO is not a part of the async runtime contract (I don't know if this is good or bad), and Tokio & futures famously have different `Async{Read,Write}` traits. I once had to do this [0] to adapt between them.

This means that any crate that uses IO will be bound to a limited number of Runtimes. Everything being Tokio-only is pretty bad (though Tokio itself is great), but here we are...

[0] https://github.com/bluejekyll/trust-dns/pull/1373#issuecomme...

I need a cert.pem and privkey.pem for https://github.com/bluejekyll/trust-dns but even using the extractor to get a cert.pem and privkey.pem from the acme.json file it seems invalid.

You might be interested in Trust DNS - "A Rust based DNS client, server, and Resolver, built to be safe and secure from the ground up."

It looks like you need to reach for a separate crate for that: https://github.com/bluejekyll/trust-dns/blob/7dcb7b983f5407d95d93b800af13caeee975aaa8/crates/async-std-resolver/src/lib.rs

You might be interested in new alternative to dig called dns https://github.com/bluejekyll/trust-dns/blob/main/util/src/dns.rs . I found out about it from https://twitter.com/benj_fry/status/1513269287229657091

I've found the Trust-DNS Resolver crate and it does the job! Now the binary seems to not use any dynamic library to look up the ip of a host.

In gr-dtv transmitter examples for Gnuradio, I see some times people use a resampler block before the RF hardware sink. Say our sampling rate is ~9.14Msps which satisfies the Nyquist criterion because our samples are complex numbers.

2.1. Thanks for that tip, I forgot that I was able to check the source code of the WBFM Receive block. As you have said, there are mostly the same. There are some differences between how values are picked. The WBFM Receive block would be a synonym of Quadrature demod => Fir Filter (decimation => Low pass filter) => FM Deemphasis. 2.3. My question there is why 10 and not 20 or 100. I understand that the idea is to reduce the sample rate asap, but what I don't understand is why those values were picked and how can I understand what would be the "correct" or "best" value. 2.4. I'm not fully understanding what you said. If I check the WB FM recieve source code the values that are supplied as the cutoff freq and transition width of the Low pass filter differ from the one of the example. The webfm would apply a sample rate / decimation / 2 - sample rate / decimation / 32 as a cutoff freq and a sample rate / decimation / 32 as a transition transition width. Calculating those values would end up in different that the ones supplied in this second example. Again, is there a rule of thumb to pick these values?.

Gaussian filter is used only on the tx side, so specifying bt in the receiver makes no sense. Take a look at gfsk mod/demod blocks implementation: https://github.com/gnuradio/gnuradio/blob/master/gr-digital/python/digital/gfsk.py

GNU Radio

Here's the filter coefficients used for the GNU-Radio interpolator block to get you started. This is a 7th order interpolator (i.e., 8 FIR taps) with very good performance. Each "row" of the array sets the delay in steps of sample_time / 128.

From their README: “open-source software development toolkit that provides signal processing blocks to implement software radios.” https://github.com/gnuradio/gnuradio