Kaitai is pretty nice. Hex editors with structure parsing support used to be more rare than they are now, so I've used https://ide.kaitai.io/ instead a few times.
Also, the newest Kaitai release added (long awaited) serialization support! I haven't had a chance to try it out.
There was a conversation on their mailing list contemplating dropping NSS support. https://curl.se/mail/lib-2022-01/0120.html If you have a use case for NSS in curl, you may want to speak up. Perhaps "I want curl to look exactly like a browser" is a significant use case?
Agreed, it is very important to bring this up on the mailing list. It might also be plausible to make curl look like Chrome if curl had BoringSSL support.
When I built an ARM based NAS, I chose to use the Banana Pi BPI-R2 because it was one of the very few boards with 2x SATA ports using PCI-E. It worked fine and got good speeds. It's difficult to run a current kernel on the BPI-R2 though (it is slowly creeping towards mainline). If I built another NAS again I'd just use an x86_64 or aarch64 SBC with a PCI-E port and connect a good SATA controller.
Technically `git push --signed` also exists which could fix the issue of rolling back commits. It would verify that the person doing the push also holds the GPG key at least. But as far as I can tell you have to manually do something with it in the post-receive hook and GitHub doesn't support it at all.
Or many of the other issues that plague archive formats: duplicate files in the archive at the same path, symlinks in the archive or relative links enabling directory traversal.
Wow, git's url bugs always seem to become easily exploitable due to .gitmodules.
I found CVE-2015-7545 a few years ago, a malicious URL using the ext:: scheme could cause code execution. It was only easily exploitable because you can ask the client to fetch any URL you want via git submodules. (This vulneriblity was fixed, and since then the entire ext url scheme was disabled by default.)
If the laptop is disconnected from AC, it hibernates. It will switch to hibernate if power is removed while already sleeping. If I want to force a hibernate manually, I just pull the power before closing the lid.
This reminds me of the time my party argued about how much modern information theory we were allowed to use in D&D. We wanted to maximize the amount of information to communicate using Sending which states that it sends "twenty-five words or less". Can I use a form of encoding and a compression algorithm? Or can we make up words and can they be arbitrarily long?
Compression schemes (in the form of code books) to save on telegraphy costs have existed almost as long as the telegraph itself.
From [1]: "Elaborate commercial codes which encoded complete phrases into single words were developed and published as codebooks of thousands of phrases and sentences with corresponding codewords... Cable tolls were charged by the word, and telegraph companies counted codewords like any other words, so a carefully constructed code could reduce message lengths enormously."
Is D&D set in a world where the telegraph exists? I've always gotten the impression that insofar as it's linked to our history of technological progression it is set well before that invention, while after the times of e.g. the Caesar cipher.
Good point. So here is a compression scheme from about 350 BC, describing how to pass messages from one mountain peak to another, using a torch and a water clock [1][2]:
"The water-clocks are an early long-distance-communication-system. Every communicating party had exactly the same jar, with a same-size-hole that was closed and the same amount of water in it. In the jar was a stick with different messages written on. When one party wanted to tell something to the other it made a fire-sign. When the other answered, both of them opened the hole at the same time. And with the help of another fire-sign closed it again at the same time, too. In the end the water covered the stick until the point of the wanted message."
Well if players want to get pedantic, in typing, a word in "words per minute" in considered 4 or 5 characters, so as the DM, clearly it's your prerogative to use that definition.
As a German: I feel that while this would potentially increase the average length of the words you "send", it probably will keep or even decrease the amount of information transferred..
Also, the newest Kaitai release added (long awaited) serialization support! I haven't had a chance to try it out.
https://kaitai.io/news/2025/09/07/kaitai-struct-v0.11-releas...