kyleomalley

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).

A quick aggregated look at common cloud status information, along with popular AI models, DNS and public CA infrastructure status.

I expect if enough of these stop working, the site will too.

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’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.

I wanted to play around with Claude cli for a bit this morning and spent about 2 hours setting up hosting and making this (obviously) satire security company website.

You have a choice here on your platforms, this isn't even remotely an honest comparison, is it?