Mentioned on the TUHS mailing list https://www.tuhs.org/pipermail/tuhs/2024-June/030151.html

Common Lisp program trying to map between Unix and Lisp concepts.

This section of the site offers RF engineers quick access to popular calculators and design aids. They are useful at design time and for training purposes, both of which stimulated their development and use over the years. Each tool is written in Javascript and the user can view the page source should they wish to examine the implementation.

I have tried to include references to the various books/papers that I have used in the development of each tool and although I have used them all at various times and believe them to be accurate, please use due diligence and further simulate where necessary.

Most of the tools come with sample values pre-entered into each input box to offer a degree of help. I apologise if this bothers you, but from the feedback I receive, it is generally preferred.

Please be sure to have read the "terms of use". The link is available at the bottom of every page.

An example from Peter Seibel's blog, see also
https://gigamonkeys.com/code-reading/
https://gigamonkeys.com/knuth-dijkstra/

Measurements with internal and external reference clock.

See README.me for instructions to set up uu{en,de}code for transferring data between emulated v7 and the host system.

This theme was mentioned on https://www.reddit.com/r/emacs/comments/1czgb5f/acmetheme_is_just_so_pleasant_to_look_at/ which I found on Sacha Chua's blog https://sachachua.com/blog/2024/05/2024-05-27-emacs-news/
https://github.com/ianyepan/acme-emacs-theme

Instructions for setting up a Raspberry π with a static IP address.
Found via https://www.sunfounder.com/products/power-pack, which was mentioned on the Raspberry π blog https://www.raspberrypi.com/news/capture-solar-eclipses-with-raspberry-pi-4-and-the-high-quality-camera/

The references look interesting.

The Language-theoretic approach (LangSec) regards the Internet insecurity epidemic as a consequence of ‘ad hoc’ programming of input handling at all layers of network stacks, and in other kinds of software stacks.  LangSec posits that the only path to trustworthy software that takes untrusted inputs is treating all valid or expected inputs as a formal language, and the respective input-handling routines as a ‘recognizer’ for that language.
The recognition must be feasible, and the recognizer must match the language in required computation power.

Found on the TUHS mailing list https://www.tuhs.org/pipermail/tuhs/2024-May/029846.html