That's exactly what he did - if you look at this history section, he was broadcasting analogue TV signals to his house, and embedding his own Ceefax service in the signal!
Very interesting tool! My Yorkshire grandfather would often say "kirk" instead of "church", which I always thought was more of a Scottish word. Doing a place name comparison of those words shows a fairly clear division of north and south - https://placenames.rtwilson.com/#W3sidGV4dCI6ImtpcmsiLCJjb2x...
I remember participating in the Domesday Project in the eighties when I was in primary school, and it inspired me to help set up similar project in 2005 (https://www.geograph.org.uk). At the time, we were in contact with the BBC to see if we could incorporate the Domesday data, and while they were warmly receptive to the idea, they concluded the legal framework under which the original data was collected did not allow for much flexibility in re-purposing it.
I'm sure I've read a much older short story, possibly by Frank Herbert, where in the future computers do all the calculations so humans have forgotten how to do basic arithmetic. It is rediscovered, only now it's much cheaper to put a human in a missile to perform guidance calculations than using an expensive computer! The HN hive mind will probably remember this better...
FWIW, I recently switched from an Intel to an M1 Macbook, and found shared volumes with Docker Desktop were unusably slow (previously, I'd used VirtualBox host docker and shared files into it via NFS).
However, using https://mutagen.io/ to keep the container in sync has worked remarkably well - it's greatly improved the speed of the container.
I have a pi with a Displayotron HAT which is designed to wake me up with a loud klaxon noise if it detects service outage. It also emits a soft glow to show that all is well.
Aside from valuing my sleep, I have a lot of incentives to ensure it never goes off, including the fact my wife says she'll divorce me if she ever hears the klaxon :D
That's a good point, and I must admit I didn't know what a route leak was or that it could inflict this kind of damage. I appreciate now it's not CloudFlare's fault, and my hat is off to the CTO for posting more detail here.
On the plus side, I did get to test the "Pause CloudFlare" button in a real-world scenario!
We've been evaluating Cloudflare mainly for doing failovers faster than DNS. This morning I ran some tests to generate graphs to show the typical delay incurred in preparation for a show-and-tell with some key people.
I started seeing delays of up to 300 seconds! At best there was a 1 second delay. I wondered if I was going to have present "Why we've decided not to go with Cloudflare!"
Any longtime Cloudflare users comment on how rare an event this sort of thing is? It seems rare from eyeballing the recent alert history.
Honestly, it's painless. Fire up a cloud server, run the omnibus installer and you're away. I can't remember having any serious issues in five years running it that way.
This is up there with the 500 mile email problem - the nature of headers inside an XLS file embedded in an email caused a signalling error in a T1 line when the email was retrieved!
I'm 47. I don't worry about age that much, but I recently had a fitness checkup at a gym. I'm no great athlete but I do run and cycle a bit. I mentioned I was training for a marathon.
The instructor, in her 30s, encouragingly exclaimed "ooh, you're doing very well for someone nearly in their 50s"