Perl should say: You are old and a nerd or you use Debian

Not all FOSS projects need to be profitable to survive. IOW if a project cannot survive without being profitable and it cannot be profitable long-term, then it cannot survive long-term.

I just replied to the other person’s comment.

I don’t. Could you elaborate?

While Linux itself isn’t proprietary, it supports loading proprietary firmware/microcode blobs and running on proprietary hardware. Thus, part of the Linux hardware/software stack is proprietary.

I’m surprised that other people are surprised that for-profit companies constantly try to increase their profits; such companies only contribute to FOSS when that’s more profitable than the alternative. The Linux kernel, AMDGPU, Steam, etc only exist because some part of the software/hardware stack is proprietary (which becomes a more attractive product as the FOSS portion of the stack improves).

I’m definitely not justifying the “rug-pulling”, but people need to stop supporting projects with no potential for long-term profitability unless those projects can survive without any support from for-profit companies. Anything else is destined to fail.

Maybe I’m Jia Tan 😉

The data block would be modified but the signature of that block can’t be recomputed without the key used to sign it

Isn’t that also true of an encrypted checksum, though? For some plaintext block q there is a checksum r, but the attacker can only see and modify the encrypted q (Q) and encrypted r (R). How any change to Q would modify q (and R to r) can’t be known without knowing the encryption key, but the attacker would need to know that in order to keep q and r consistent.

I’m not a cryptographer (so maybe this is wrong), but my understanding is that although it’s possible to modify the cipher text, how those changes modify the plaintext are very difficult (or impossible) to predict. That can still be an attack vector if the attacker knows the structure of the plaintext (or just want to break something), but since the checksum is also encrypted, the chances that both the original file and checksum could be kept consistent after cipher text modification is basically zero.

I vaguely remember the advice actually being to leave it running but disconnect it from the internet. Although maybe hard disconnect the backups if you can.

…Because no one else wants to write my documentation.

There was a thread about that on c/selfhosted a few weeks ago. Created by a particular wild-cat-inspired sysadmin, I might add.

But on a more serious note, the interactions between a sysadmin and their servers (that they have enough responsibility for to be able to name) are much more intimate than the interactions between a dev and their variables. The server names also exist in a much larger namespace, so they need to be more unique.

deleted by creator

Because you’re generic and everyone’s initialized you at some point

To be fair, most non-porn “NSFW” is probably “NSFL”. So NSFW in its exclusive usage is almost entirely porn.

Meh, it’s a hobby. Lots of people talk about their hobbies.

Still a funny comic, though.

SMH my head

That’s what my “friend” did. Reddit banned every account he used on his phone at once, but with a different IP, desktop browser, and cookie isolation, they haven’t noticed so far. He might sound like some professional troll, but he was actually banned for a stupid reason.

Reminds me of lolcode:

HAI 1.2
CAN HAS STDIO?
PLZ OPEN FILE "LOLCATS.TXT"?
    AWSUM THX
        VISIBLE FILE
    O NOES
        INVISIBLE "ERROR!"
KTHXBYE

If you mean initiating connections from one computer on your local network to another, you need to install and enable avahi-daemon (or some other mDNS daemon) on the “fancy” one. Your router also needs to support and enable mDNS forwarding, but basically all of them do by default. Then just use your-hostname.local in place of the local IP address, and your computer will automatically resolve it using mDNS. It’s different than regular DNS, so it doesn’t need any special configuration to use it. And word to the wise: don’t use uppercase or special characters in your hostname.