If you are using filter scripts, to block specific domains or script payloads, that extension can't load on a properly secured CSP page. And that page may be using CSP to protect throwing up ads... Or malware.

The video of the Four Buffs might help you understand this better. [0]

There was an extra cable, containing a photo diode, that you just stuck to the screen itself.

[0] https://youtu.be/xxo1Gs46ti0?si=fqPIaxaHGFFFJmpF

> Colossal’s dire wolf work took a less invasive approach, isolating cells not from a tissue sample of a donor gray wolf, but from its blood. The cells they selected are known as endothelial progenitor cells (EPCs), which form the lining of blood vessels. The scientists then rewrote the 14 key genes in the cell’s nucleus to match those of the dire wolf; no ancient dire wolf DNA was actually spliced into the gray wolf’s genome. The edited nucleus was then transferred into a denucleated ovum. The scientists produced 45 engineered ova, which were allowed to develop into embryos in the lab. Those embryos were inserted into the wombs of two surrogate hound mixes, chosen mostly for their overall health and, not insignificantly, their size, since they’d be giving birth to large pups. In each mother, one embryo took hold and proceeded to a full-term pregnancy. (No dogs experienced a miscarriage or stillbirth.) On Oct. 1, 2024, the surrogates birthed Romulus and Remus. A few months later, Colossal repeated the procedure with another clutch of embryos and another surrogate mother. On Jan. 30, 2025, that dog gave birth to Khaleesi.

The process seems to have dictated this. They needed an easy surrogate, a dog, and wolves required no need of introducing anything new into the genome, it's "just" reactivating what is already there.

That particular show was broadcast on Channel 4 in the UK, at 6PM. So when most people were watching the news on a Channel 1.

Channel 4 was mostly just advertising, at the time. This show is selling you on computers. It's just that what they were selling was awesome.

Coming from the other direction, luarocks binding to just one version of Lua, is an absolute pain in the ass.

I've got some libraries that support five or six different versions of Lua. Building packages for all of them basically means throwing luarocks out the window, because linking to multiple Lua runtimes ti=o luarocks does all kinds of truly heinous things.

You can end up with the library and headers linked from different runtimes, simply because it isn't following what the local system says is available.