Is this page geo-locked? All I get is a "403 forbidden" when I try to access it from the UK.

There's something in the sidebar saying it's currently broken on mobile. I guess I see it because I'm on a desktop browser then.

I was using a desktop browser.

All I get is a 403 forbidden when I try to access this page.

It's there for sure. However, it's not particularly relevant to the following two points:

1. The author should be able to do whatever he wants with his own device. That he owns.

2. The author should be able to decline consent for data-gathering activities and general AI stuff that he doesn't want.

See the Doomsday algorithm, discussed elsewhere on this thread. https://en.wikipedia.org/wiki/Doomsday_rule

Or if you have a limited supply of gunpowder but a way to make sufficient numbers of appropriately shaped projectiles, an air rifle would do the job and is much lighter and simpler than a trebuchet.

Isn't it true that you can never generate a supersonic projectile with just air pressure?

I don't believe that is true - rockets produce a very supersonic airflow from gas pressure.

I looked into it. Yes, you're correct, I was wrong. Although there is a speed limit of mach 5 (theoretical, not reachable in practice!) for shockwaves in normal atmosphere.

There was a fellow student at university who put the entire Hunting Of The Snark in their .plan file. It scrolled for a while.

Did the author forget to add pictures? They seem to be referred to in the text.

The images don't load without javascript, which sadly is customary for the modern web experience.

Which pictures are you missing? I see three stills from the Bladerunner intro sequence, and two embedded videos of it.

One of the meeting rooms here at work has a couple of big panels for displaying presentations, and they're regularly misinterpreting noise on some line or other and changing their brightness/contrast/etc settings. It's highly annoying. I imagine there's some kind of data line plugged into the TVs which is picking up interference and causing them to freak out.

There was also an issue with Linux about 8 years ago where the THP daemon would start busy-looping searching for pages to amalgamate, wasting loads of CPU time (and I believe freezing the processes it was inspecting), and so people were advising switching off THP for that reason until it was fixed. It hit our large Java processes quite badly.

Software that tried to implement memory protection or virtual memory on the Amiga had to have a huge long hit-list of software that set the AllocMem flags incorrectly and had to be treated differently. That's because the MEMF_PUBLIC flag didn't really do anything on the base OS, so programmers didn't bother using it correctly.