This really does not need to be that hard. For TLS, many tools support setting the SSLKEYLOGFILE environment variable to log the session keys used in connections. Wireshark can import those to decrypt everything. [1]
Unfortunately, nothing exists for SSH (yet?). [2]
I do agree that if you design a protocol that enforces encryption, you should include some debugging interface. It is much more straightforward to do this by logging the session secrets on the endpoints rather than trying to break it through a man-in-the-middle, the main thing the protocol is protecting you against.
> You can't even access the data without locking the mutex.
It's even nicer than that: you can actually access data without locking the mutex, because while you hold a mutable borrow to the mutex, Rust statically guarantees that no one else can acquire locks on the mutex.
> 4.5/o3 doesn't seem hugely more intelligent then 3.0 -- it hallucinates less [...]
This is not entirely true, or at least the trend is not necessarily less hallucination. See section 3.3 in the OpenAI o3 and o4-mini System Card[1], which shows that o3 and o4-mini both hallucinate more than o1. See also [2] for more data on hallucinations.
Apparently, this is not always implemented correctly on SSDs. It should take quite some time, but if it finishes after a few seconds, it probably didn't really wipe your SSD securely.
Command driven configuration. Everything is scriptable. It also uses a binary tree structure for managing splits, and I found out that I liked that more than the way i3 does it.
Unfortunately, nothing exists for SSH (yet?). [2]
I do agree that if you design a protocol that enforces encryption, you should include some debugging interface. It is much more straightforward to do this by logging the session secrets on the endpoints rather than trying to break it through a man-in-the-middle, the main thing the protocol is protecting you against.
[1]: https://wiki.wireshark.org/TLS
[2]: https://gitlab.com/wireshark/wireshark/-/issues/16054