VoLTE and SIP do indeed retail a lot of the concepts of circuit switched. The challenge is that now you have the complexity of (seemingly invariably) a Telco managing a k8s stack on an OS they don't understand, and which has hundreds of CVEs per month they aren't patching. The failure modes of VoLTE/SIP are also a load more complex than CS domain issues - IMS interop issues and XML parsing delights await!
So I guess it's not only about getting off the internet - there is a real shift in complexity in these more modern stacks too.
That’s not true at all. Yes to the k8s but at least at my work we are scanned to death as soon as a new IP comes up on our network. Plus we have golden image updates at least every 30 days. We couldn’t even get SNMP traps out of our virtual firewalls because of “security”.
Containers are 10x better than monitoring and supporting some 30 years old switch in a central office that consumes more power than my cul de sac.
You are not wrong about the complexity of modern stacks.
However, VoLTE predates k8s adoption in most telcos and the physical network appliance == NF model is still alive and well, so it’s not necessarily a fair comparison. You’re also right about the added complexity of SIP/RTP (let’s agree not to talk about MMS lol).
You don't need to go out and buy hardware keys today. You should be able to use any FIDO2 key these days for SSH, as long as your server runs a recent enough OpenSSH server, which supports ecdsa-sk or ed25519-sk public keys.
Reputable vendors of those hardware keys included Yubikey and Token2, among others. You are really just using them as FIDO2 tokens, so go for what's reputable there.
If you are just getting started, you can generate and use software-backed keys (using ssh-keygen) and copy the public keys to servers' authorized_keys file using ssh-copy-id (or manually adding it). You should probably start learning this way (with plenty of online guides, and fewer risks of an old server implementation not supporting FIDO2 credentials), and then move to hardware keys once you understand the mechanics of copying around public keys, etc. Your password manager might also support acting as an SSH agent for key based logins - I believe Bitwarden and some others now do this, for example.
You could also do mutual authentication of SSH, with a local password-encrypted private keyfile, if you really like passwords. That gives you all the benefits of the "something you know" factor, without exposing the password to the server. And you can inspect how the decryption and use of the key happens (since it is on your computer), and therefore see it doesn't leave your computer.
The data broadcast from ADS-B includes both GPS position (Lat + Lon) and altitude. If you created a bounding box, you could add a height parameter to make it 3D, and get a list of such aircraft and the timestamps of their transmissions while inside that (3D) bounding box.
That wouldn't be too difficult to do with a little bit of filtering of the feed coming out of an ADS-B receiver.
An RF receiver is not required for the subject use case, they can use existing ADS-B IP feeds, process the feed (either live or with historical data) according to the 3D bounding box, and generate reports based on flight paths intersecting the bounding box.
So I guess it's not only about getting off the internet - there is a real shift in complexity in these more modern stacks too.