Years ago, we used to use Etherpad for that. Don’t know if that’s still a thing.

Well, in PHP you cannot #define new words from some new language to mean basic language keywords.

If any person actually typed that they aren’t sane at all.

That doesn’t actually rule out anything.

You just gave me flashbacks to that abomination of a programming language they call sqf.

“Squeezes”, “20%”. Interesting word choice. Feels almost like downplaying. When, in reality, 20% is massive, especially on a CPU like the Threadripper.

Going by what OP thinks “Chaotic Evil” means for sysadmins, they have clearly never heard of BOFH.

Writing good comments is an art form, and beginner programmers often struggle with it. They know comments mostly from their text books, where the comments explain what is happening to someone who doesn’t yet know programming, and nobody has told them yet that that is not at all a useful commenting style outside of education. So that’s how they use them. It usually ends up making the code harder to read, not easier.

Later on, programmers will need to learn a few rules about comments, like:

• Assume that whoever reads your code knows the programming language, the platform and the problem domain at least in general terms. You are not writing a teaching aid, you are writing presumably useful software.
• Don’t comment the obvious. (Aside from documentation comments for function/method/class signatures)
• Don’t comment what a line is doing. Instead, write your code, especially names for variables, constants, classes, functions, methods and so on, so that they produce talking code that needs no comments. Reserve the “what” style comments for where that just isn’t possible.
• Do comment the why. Tell the reader about your intentions and about big-picture issues. If an if-statement is hard to parse, write a corresponding if clause in plain English on top of it.
• In some cases, comment the “why not”, to keep maintenance programmers from falling in the same trap you already found.

As someone who is in tech… not sure, either.

Well passwordless.

Same thing in this context. But sure, an encrypted partition would work.

Dunno about ideal, but it should work.

It does have quite a bit of overhead, meaning it’s not the fastest out there, but as long as it’s fast enough to serve the media you need, that shouldn’t matter.

Also, you need to either mount it manually on the command line whenever you need it or be comfortable with leaving your SSH private key in your media server unencrypted. Since you are already concerned with needing to encrypt file share access even in the local network, the latter might not be a good option to you.

The good part about it is, as long as you can ssh from your media server to your NAS, this should just work with no additional setup needed.

Interesting. Though it does seem to to require your private key to be unencrypted…

Is sshfs an option? Unfortunately, I don’t think you can put that into /etc/fstab, though…

Wait, they managed to forge Let’s Encrypt certificates? While it explains the attack on TLS (though technically not https as originally claimed, not that it makes much of a difference), that’s even worse…

Really? That’s a rather big claim, and would change a lot for me if true. Do you have anything by the way of a source?

Also, how do you MITM https traffic without one of the parties just handing you their keys?

In your case, instead of getting a dedicated server and putting proxmox on it, I would check if it might not be cheaper to just get individual virtual servers directly.

Other than that, sure, I have been a customer for many years now, and I have always been a fan of Hetzner’s price to quality ratio.

One of the advantages of being on old reddit like a hopeless geezer is not getting to see that shit.