Amatuer radio is interesting. It does remind me of the earlier wild west days of the internet. There are no bots, nothing commercial, and you can just “rag chew” with real people or do contesting where you try to reach further distances or make contacts in certain areas. Most of it is only as hard as you want to be but it’s such a vast and complex environment (licensed and unlicensed stuff). All of it is fun. Far enough away from computers that it’s all mostly (and technically always should be) a real person at the other end talking — but that will change soon enough I’m sure.
I probably use Reddit 1/10 as much as I used to as well. Kind of sad seeing Reddit going down the enshitification path that seems like most software and apps tend to do.
Question: what about the other trusted roots? Has anyone tested them?
I’ve tested most of them (from historical archives) and have automated testing any new CA certificates that show up in CT.
I’m calling the check “luggage code entropy” (1 byte).
It was a mistake to trust so many root CAs and misapply the same level of trust where clearly it is impossible to independently verify and most of the accountability is smoke and mirrors. We need to be asking “why” here, the stated reason needs to be much more than “because webtrust audit” and “we recorded the entire operational process for key material handling on YouTube with this open source implementation of key ceremony tooling and have underwritten the strength of the private key with a few $mm dollars, to be paid out to the rest of the roots for the shared reputational damage to the entire ecosystem should we fuck up (intentional or otherwise).
My impression is "why" is political, with regulations like EU's eIDAS and other national digital sovereignty efforts setting the rules. It's not even WebTrust that's the target in most cases, it's the ETSI EN 319 series and ISO 21188.
Is it possible to convince the EU to say that, no, each one of your 27 member states isn't allowed to have a PKI? I don't think so.
Strange seeing how people have such a hard time seeing others using AI and seem to want to complain about it instead of just, well, asking AI why something was likely done a way. It works both ways my dudes, experts don’t need to explain every last detail, prompt a bot with the context until you understand.
From my prospective, the outputs of a bot aren’t the interesting bits, it’s the input prompt that should warrant more attention.
It might be kind of overlooked when people read about the big scary results from mythos; the real breakthrough was probably just as much the application of the (very decent) model through a well engineered wrapper (harness). Other models including codex or glm result in significant findings as well.
If you haven't been following MeshCore, it seems to be really hitting strides with adoption and growth. There are scaling issues [1] and overall the protocol has its limitations[2] , but its really interesting to play with and cheap, which is helping fuel adoption. Since devices are cheap and software is too, so given enough time, it is likely these issues can be sorted out (and it may not even look or smell like what we're working with now, as long as people can upgrade firmwares and software)
On the west coast of the US, there is a consortium of independent networks that are likely to merge (to some degree, TBD). https://www.wcmesh.com/
I'm in SoCal right now and while this network is impressive, the Cascade network is really really awesome (I was able to use it first hand last week!). https://cascadiamesh.org/
One of the challenges that remains unsolved is how local networks are forming around non-default-for-the-region settings and making those well know or obvious to new users.
Take away from the map from analyzer.letsmesh.com for today is that ohio is extremely overrepresented, why? This weekend is Hamvention!
I regularly use about half a dozen programs that interface with radio equipment. Most of it works but getting it all working together is extremely complex.
Since primarily interested in FT8 and MeshCore here in the local SoCal MC region (wcmesh.com) I put together a Pure-Golang implementation to combine both modes into the same GUI client. The FT8 modem might be the only functional Golang decoder right now, unsure, but it’s entirely open source and here:
It’s unclear, my next step is taking the few days worth of recordings along with the ground truth that you can get from ‘jt9’ and giving Claude the task. I’ve been running decode shootouts on 128c aarch64 and made some progress but I needed to finish the UI.
Im going to take all of the data and use it for a corpus for training and see if I can get a small model built that can run easily on mac arm64
I wanted something better than WSTJ-X and Gridtrackr with the endless knobs and complications and developed this along with my favorite french intern (Claude).
The /lib/ golang FT8 library is not yet complete and struggles with around 15% of the decodes that WSTJX will get at very low signal to noise ratios (-18 to -25). But otherwise matches at around 85%.
If you have an newer ICOM or Yaesu radio and use MacOS, you can simply just run the program, configure your callsign and LOTW logins and you are off. Every logged QSO goes into a standard ADIF file that gets signed/uploaded automatically and DXCC grid tracking can be enabled on the map overlay.
The waterfall scope overlay is my favorite feature though as you can live watch decodes and quickly cross reference what you see, get magnified view of a decode and do QRZ lookups etc directly on the waterfall.
reply