Even better quote, I love using this one.

“So, with AI writing code for us, all we need is an unambiguous way to define, what all our business requirements are for the software, what all the edge cases are, and how it should handle them.”

“We in the industry call that ‘code.’”

KeePass on my phone and desktop, with the master file sync’d automatically to the server in my basement.

The XZ exploit was found because some dude was investigating performance issues in a system, and noticed an unusual amount of time being spent in SSH processing, IIRC.

I’ll take this over the more “classic” styles, when people seed to believe they were paying the compiler by the character.

Generally speaking, fault protection schemes need only account for one fault at a time, unless you’re a really large business, or some other entity with extra-stringent data protection requirements.

RAID protects against drive failure faults. Backups protect against drive failure faults as well, but also things like accidental deletions or overwrites of data.

In order for RAID on backups to make sense, when you already have RAID on your main storage, you’d have to consider drive failures and other data loss to be likely to occur simultaneously. I.E. RAID on your backups only protects you from drive failure occurring WHILE you’re trying to restore a backup. Or maybe more generally, WHILE that backup is in use, say, if you have a legal requirement that you must keep a history of all your data for X years or something (I would argue data like this shouldn’t be classified as backups, though).

Can I get an Oracle version?

Discord gained popularity and maintains it, in spite of the many reasons to avoid it, because of usability and feature richness. Slack, Teams, Matrix, Telegram, they are miles ahead of everyone else in the live-chat space, when it comes to user experience.

This was an interesting article about some tech I’ve never heard of before, but it has little to nothing to do with Discord’s overall success.

rsync, for sure. That’s what I used when I had to migrate a 10TB datastore to a new machins.

A DNS Proxy/Forwarder server? That’s where you would configure how your .internal domain resolves to IPs on your internal network. Machines inside the network make their DNS queries to that server, which either serves them from cache, or from the local mappings, for forwards them off to a public/ISP server.

it makes them completely inaccessible to client side JavaScript

Dude literally said to do this for browser clients, and only support bearer tokens for non browser clients.

The Apache 404 page doesn’t really seem that interesting.

Fair enough.

I like TypeScript less for its ability to categorize my grocery list and more for its ability to stop anyone from putting cyanide on it.

I know nothing about any of the other alternatives mentioned here, but I’ll pitch in my 2 cents that I am very happy with OMV. Haven’t had to touch it since they day I set it up, maybe 2 years ago. Except one time when I wanted to add a new SSH/FTP account for someone.

In addition to the core file services, it supports running a Docker host, in which I have running instances of Portainer (a Docker Web UI), Transmission (a bittorrent client, woth VPN support, also with a Web UI), and Plex.

/shrug

That’s my best guess, in the sense that that’s what the compiler ends up producing, for templated code: the same code copy-pasted for however many different use cases you have.

I think templates is what he’s making fun of.