The amateur radio community is very aware of the problems and several initiatives have been launched to quantify the effects. One of them is the DARC's ENAMS, which is described in detail here:
https://web.tapr.org/meetings/DCC_2020/DK5HH/F_ENAMS-DCC-DK5...
But then again, if the people who carelessly include 3rd party dependencies (i.e. playing with fire) are those who use CF... they probably won't object to it :-)
In order to create interference between two radars, the ramps have to overlap pretty exactly, within a few nanoseconds of each other. This is very unlikely to happen.
Modern radars employ technologies to detect and/or avoid such collisions.
Overall it is not really an issue, even with many radars in crowded spaces.
By filtering for a few keywords, you can get of 99% of the form spam.
Deliverability has never been an issue for me since (of course) I run my own mail server. But I doubt it's a serious issue when you take the little time it takes to set up DKIM etc.
I wouldn't make it more complicated than it has to be :-)
This SDR won't be able to compete with expensive high performance receivers that have a lot of pre-selection, but there are many examples of low cost SDRs that do a surprisingly good job on the HF bands (without too much pre-selection).
I suppose the performance in the HF range will be similar to KiWiSDR, AirSpy, or the RedPitaya. If you want to know how well they work, there are many KiWiSDRs online to listen to :-)
The interesting part is certainly that it delivers 50 MHz bandwidth up to 6 GHz, which exceeds e.g. what the ADALM Pluto can do.
Certainly an interesting product at an attractive price tag. I consider getting one!
Morse code "dah-di-di-dah-di, dah-dit" ( –··–· –· )
IMHO more common is to send "ESE" (. ... .) - and the other station replies "EE" (. .)https://lcwo.net/ext/player?z=MjR%2BfjIwfn42MDB%2BfkVTRSBFRQ...
"ESE" is a popular Amateur radio call-sign suffix among Morse enthusiasts for that reason.
Not generally useful to show this by default, because nowadays most pages are dynamically generated and although it's technically easy to implement, the last modified header is typically not set to $now.