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.
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.
Security Engineering is mostly about control and minimizing attack surfaces. Apple iOS implements this exceedingly well, with defaults, while still being one of the most widely used platforms on the planet. I believe IOS gets it right the vast majority of the time with solid architectural changes and not just endless patches and knobs that are hidden and forgot about. This is the key difference of "It just works" verses other platforms.
If someone wants to run another platform, go for it. Of course are shortcomings in iOS (as with any system), but viewing entire problem space of security and privacy, the default install of IOS + Safari could rarely be any better for the average consumer. This is why Security and Privacy is literally a paid feature of the IOS platform, and anecdotally everyone professional I know (who isn't in tech) is using IOS devices.
Personally, I'm planning to blocking RCS and any third party app stores on any of my own (and families) devices -- again, control and minimizing attack surfaces and eliminating an entire class of issues is better than trying to manage them to no end.
Harness example: https://github.com/evilsocket/audit