1. The freedom to run the program as you wish 2. The freedom to study how it works and modify it (which requires access to source code) 3. The freedom to redistribute copies to help others 4. The freedom to distribute modified versions, so the whole community benefits from your improvements

To my mind ... GenAI coding make all of these far more realizable, especially for "normal people", than CopyLeft ever has. Let's go through them ...

Want to run a program as you wish? Great! It's easier than ever to build a replacement. Proprietary or non-free software is just as vulnerable to reimplementation as Copyleft is.

Want to study a how a program works and to modify it? This is now much more achievable.

Want the freedom to redistribute copies to help others? Build your own version! It may not even be copyrightable if it's 100% generated (IANAL).

Want to distribute modified versions? yes! see previous.

I dunno; seems like generative coding can be as much a liberator as any kind of problem.

Here's my Translations of the Chapter titles. I'm pretty sure many of these have old-Irish style séimhiú (a dot above a consonant denotes what would now be a h after the consonant) in the originals that have not been translated by the OCR, so there are several missing h letters. If I weren't on a plane over Afghanistan, I'd download the PDF to check. Will update the repo when I can!

   Pláinéid na feaca Súil Duine riamh = A planet no person's eyes have ever seen
   An Radarc, tríd an gCiandracán = the view throughout the [Ciandracan] (this is a compound proper noun, "Cian" is "head" or "brain" and "racán" could be visor or rocket)
   An Turas go Manannán = the Trip to Manannán
   Manannán = Manannán (it's a noun, which is very similar to the Irish term for the Manx and the Isle of Mann). 
   Muintear Manannáin = the people of Manannán
   na 'Cráidmí' = the Craidmi (I think it's just a plural noun)
   An tÁrd-Máigistir = the high Magistrate, or possibly the supreme magistry
   An Priorún = the Priory
   Oidce sa Coill = The class/lesson/teaching in the woods/forest
   An tinneall = the fire
   Oidce tar Oidceanta = Lesson upon lesson
   Lug Lám-fada = the long-armed lug
   An Tróid leis na 'Cráidmí' = The war with the Craidmi
   Diogaltas = Revenge
   An téalod = not sure about this one

Nashville has plenty in the evenings, and then you can find hot spots in some cities. I've seen regular buskers in Boston, Seattle, Sarasota, and Boulder - usually in pedestrianized touristy quarters.

According to the court order, he entered the US on the Visa Waiver Program in 2009. He may have a work permit now because anyone can file for an Employment Authorization Document (EAD) through an I-765 while they are applying for a green card through marriage, but there's no indication that he had work permits before that. I've encountered Irish people throughout the US in similar situations.

https://blog.cloudflare.com/zone-apex-naked-domain-root-doma... , and I quote directly ... "Never one to let a RFC stand in the way of a solution to a real problem, we're happy to announce that CloudFlare allows you to set your zone apex to a CNAME."

The problem? CNAMEs are name level aliases, not record level, so this "feature" would break the caching of NS, MX, and SOA records that exist at domain apexes. Many of us warned them at the time that this would result in a non-deterministic issue. At EC2 and Route 53 we weren't supporting this just to be mean! If a user's DNS resolver got an MX query before an A query, things might work ... but the other way around, they might not. An absolute nightmare to deal with. But move fast and break things, so hey :)

In earnest though ... it's great to see how now CloudFare are handling CNAME chains and A record ordering issues in this kind of detail. I never would have thought of this implicit contract they've discovered, and it makes sense!

On the IPv6 side; by 2002, nobody was really experimenting with A6 records any more, and EUI64 was needless. Both were parts of IPv6 designed to facilitate "easy" renumbering, so that single prefixes could be replaced with larger ones. But the ISPs weren't complaining any more about table size.

Yes, languages do lack good mechanisms to mark variables or sections as needing constant-time operation ... but compiler maintainers could have taken the view that that means all code should be compiled that way. Now instead we're marking data and section as "secret" so that they can be left unoptimized. But why not the other way around?

I understand how we get here; speed and size are trivial to measure and they each result in real-world cost savings. I don't think any maintainer could withstand this pressure. But it's still deliberate.

Both the FFDH and ECDH key agreement algorithms are vulnerable to quantum crypt-analysis; someone capturing traffic today could later break that agreement and then decrypt the data. An attacker would have to capture the entire session up to the "point of interest" though.

This is why FFDH/ECDH are being augmented with Post-Quantum secure KEMs.

Watching Hank Green's YouTube video where he found out that his cloudy pee was cancer leaving his body, he was surprised that doctors don't tell you to expect it. It can be such a morale boost.