That's not true, in the big cloud company I work for all our 286s MFM hardrives now use upgraded RLL controllers.

Who is "they" ????

Nobody but me has physical access to that server and it doesn't accept any connections from anywhere. But yeah, you could set zfs permissions for that and use a non-root user if you wish.

You need to make a clone of a snapshot. Then, you write that to tape, then you need to make at least md5sums of the disk image or of each file on the clone, read the tape you just wrote and compute checksums of the tape as well, then finally compare the checksums.

That's always what I did when using tapes and that's still what I do with usb connected hard drives I use nowadays instead for critical stuff on top of what I described above.

I have had and I still get regular but very occasional checksum failures comparing. You can't just write to tape and consider it a valid backup without comparing with the original before putting it away and moving it to a different location. When I get a checksum failure, I run the test again to make sure I get the same exact two different checksums again to insure the problem doesn't come from another hardware component like memory scsi/sata/usb controller, bad cable etc. etc.

While at it, take snapshots on the remote server to prevent against ransomware attacks and your prod server shouldn't have any access to the replication server in a different geolocation otherwise hackers will delete/encrypt data on the replication server too. The replication server should pull the data from the prod server with something like this:

CMD_OUTPUT=`ssh -C -l root -p 52812 $HOST zfs send rpool/data/${ZVOL}@${NEW_SNAP_NAME} | zfs recv rpool/datarep/${ZVOL} 2>&1`

I know it's possible to give the prod server access to the replication server like in the proxmox backup server architecture and set permissions on the replication server so snapshots can't be deleted but I find it much more safer to protect the replication server in its own VLAN and protect it almost like a CA and insure nobody and nothing has access to the replication server.

More on topic, I think cloud customers should be aware that if their datacenter is destroyed, they *will* lose data if they didn't take care of replicating their data to a different geolocation.

Exactly the same happened when an OVH datacenter caught on fire in France. Many customers which didn't have replication set to a different geolocation lost their data. Heck a dude I know had backups on different servers in the same datacenter which turned out to be useless.

I replicate my filesystem to different geolocation at least every 10 minutes and I have pseudo real time replication (usually below 1 seconds) database replication with log replay.

Me neither but I ordered 3 dozens to take the RAM out of them and put it in my Beowulf cluster. At $1,299 for 1TB, it's really a steal at that price for 1TB

From TFS:

Indeed, a tty? who needs that? I just catch the keyboard interrupt and I write directly to B000:0000 memory address to display output.
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.phatcode.net%2Fres%2F2...

My cell phone is pretty much blank since I barely use it for anything but phone calls. People don't even text me since they don't have the number and the ones who do know that I don't check it regularly and that it's often completely off. I have a ring group on my PBX which rings my cell phone as well.

Try with such a phone at a border crossing to see how much suspicion you will raise! They then go into more detailed questioning and verifications etc. I now have to put *some* stuff on it not to raise suspicion and get through more quickly.

You will be lucky if you find an old copper penny nowadays. They haven't been made out of copper since quite a while.

No, if that current collapse, Europe is going to freeze. That current cools down Northern America and warms up Europe. That's why you have snow storms and it's cold in Montreal in the winter while comparatively a lot warmer in Paris France and Paris is farther up North than Montreal.

Paris 48.8567 N
Montreal 45.50889 N,

I am not sure it would be considered a "third party JavaScript tool". Once you gave the key to your domain to cloudflare, the domain resolves to a cloudflare IP and cloudflare act as a reverse proxy contacting to your site thus enabling them to inject any javascript without being viewed as third party.

Well I guess; download image from X, modify image with AI, upload image to X. Same can still be done on Instagram.

Sure but seriously, this is the FSF and they just found out about ipset which I have been using for decades?
From TFS:

Also no, five million entries in ipset do not generate five million firewall rules. That's the whole concept. Only one rule in the firewall can check if the src ip, dst ip, ports etc. is in the ipset. It's basically just a lookup in a hashtable that requires only 1 firewall rule.

Exactly, I can put my repo on a CD all my myself if I want too.

Not really thank God. We still manage this by ourselves with apache reverse proxies and mod_security + mod_qos coupled with geolookups and iptables ipsets basically. It works fine for us and the last thing we need is cloudflare and showing "confirm that you are human" to people visiting the sites we host.

But yes, without anything, our most busy sites would get maybe 60% useless traffic while the less busy ones would probably get something close to 99% useless traffic.