It probably sucks for you if the proposed powerline goes through your house, but the need of the many come first.

Having cheap and plentiful power is a huge market advantage. It was one of the factors driving Norway out of poverty 100 years ago.

Somewhat tangential...

I once worked for the national archives. Unlike libraries, the archives typically have the only copy of a specific piece of data. So if the lose the data, it is lost forever. My mission was to figure out how to deal with information storage in a millennial perspective.

There are tons of really interesting ways to store data. I think my favorite was printing QR codes on microfilm and then storing the film in an abandoned coal mine on Svalbard. The first frames on each roll with come with source code and instructions on how to decode the data.

FWIW; my recommendation was 3-way replicated object storage, until more stable form of storage presents itself and becomes reasonable.

I can't say it has helped much, though. Fable is still completely useless for securing code. Opus does an OK job, though.

The people deserve the credit. Not the state.

It took me about four years to fully understand my condition. Hope you figure out what is bothering you. The body is incredibly complex.

It got smashed by customs. Literally.

4-8 cores is no problem at all, though.

Then I got to experience the click of death and the internet connection was bumped to 100Mbit and I didn't need to replace my zip drive.

Then, say if the motherboard gives up, you have to do quite a bit of work to get it replaced, you might be down for hours or maybe days.

For a single server I don't think it makes sense. For 8 servers, maybe. Depends on the opportunity cost.

It should be fixed fairly quick.

And yes, I think the ergonomics are bad. Having varnish lose visibility into the transport means ACLs are gone, JA3 and similar are gone and the opportunity to defend from DoS are much more limited.

Crypto used to be expensive in 2010. It is no longer that expensive. All the serialization, on the other hand, that is expensive and latency is adding up.

Every single HTTP server in use out there has TLS support. The users expectation is that the HTTP server can deal with TLS.

but I truly appreciate the feedback. I'll reach our to the team working on this and see if I can make this a bit clearer.

Now that Varnish has been renamed, Varnish Software will keep what has been referred to as a downstream version or a fork, which has TLS built in, basically taking the TLS support from Varnish Enterprise.

This makes Hitch a moot point. So, I assume it'll receive security updates, but not much more.

Wrt. separation of concerns. Varnish with in-core TLS can push terabits per second (synthetic load, but still). Sure, for my blog, that isn't gonna matter, but having a single component to run/update is still valuable.

In particular using hitch/haproxy/nginx for backend is cumbersome.

TLS is a primary concern on the internet today.

I would recommend migrating off within a year or two.