QUIC is a really nice protocol as well, I find. It basically gives you an end-to-end encrypted & authenticated channel over which you can transport multiple streams in parallel, as well as datagrams. A lost packet in a given stream won't block other streams, and the overhead is quite low. Both ends of the connection can open streams as well, so it's really easy to build bidirectional communication over QUIC. You can also do things like building a VPN tunnel using the datagram mechanism, there are protocols like MASQUE that aim to standardize this. Apple is using a custom MASQUE implementation for their private relay, for example.
HTTP/3 is a protocol on top of QUIC that adds a few more really interesting things, like qpack header compression. If you e.g. send a "Content-type: text/html" header it will compress to 2 bytes as the protocol has a Huffman table with the most commonly used header values. I found that quite confusing when testing connections as I thought "It's impossible that I only get 2 bytes, I sent a long header string..." until I found out about this.
> The animals thrived on the swampy peninsula, gorging themselves on a root called tuckahoe that, as one historian wrote, “burns the mouth of a human being like fire.”
I'm always curious about native foods so I looked this up. The plant is probably Peltandra virginica, which was supposedly eaten by indigenous people.
> The plant is rich in calcium oxylate, this is toxic and if consumed makes the mouth and digestive tract feel as though hundreds of tiny needles are being stuck into it. However, calcium oxylate is easily destroyed by thoroughly cooking or drying the plant
https://practicalplants.org/wiki/Peltandra_virginica
I assume they mean calcium oxalate, which is also present in many food crops that must be cooked (e.g. taro root and the fruit of the peach palm).
