lazynooblet

I installed LTSC on a device recently. Very little effort for bloat free Windows.

Free Palestine.

The Gaza war is genocide.

Fuck the IDF.

Please prevent me from visiting the genocide loving USA.

This. Some people don't realise how ridiculously easy it is to change a lock when you can open the door with a key.

1. Put the working key into the lock

2. Undo this screw

3. Turn the key slightly back and forth whilst pulling the cylinder out until it starts to come out. Then just pull it all out.

4. Mark which side was front and back

5. Measure from the middle locking mechanism of the cylinder to the ends.

6. Find a lock with the same lengths. It'll be like 60/40 (100mm total length).

6b. Optional: get one with a fixed turnkey on the inside.

7. Replace lock by reverse.

What the hell that is hilarious

I hear you. I worked for an msp where some customers would refuse to invest in backup solutions and we either declined to renew their contract or they suffered an event and we were then setting up backups.

I was in the middle of a migration from OVH to Hetzner. I knew I had good backups at home so the plan was to blow away OVH and restore from backup to Hetzner. This was the mistake.

Mid migration I get an alert from the raid system that a drive has failed and had been marked as offline. I had a spare disk ready, as I planned for this type of event. So I swapped the disk. Mistake number 2.

I pulled the wrong disk. The Adaptec card shit a brick, kicked the whole array out. Couldn't bring it back together. I was too poor to afford recovery. This was my lesson.

Now I only use ZFS or MDRAID, and have multiple copies of data at all times.

I'm lucky enough to run a business that needs a datacenter presence. So most my home-lab (including Lemmy) is actually hosted on a Dell PowerEdge R740xd in the DC. I can then use the small rack I have at home as off-site backups and some local services.

I treat the entirety of /var/lib/docker as expendable. When creating containers, I make sure any persistent data is mounted from a directory made just to host the persistent data. It means docker compose down --rmi all --volumes isn't destructive.

When a container needs a database, I make sure to add an extra read-only user. And all databases have their container and persistent volume directory named so scripts can identify them.

The backup strategy is then to backup all non-database persistent directories and dump all SQL databases, including permissions and user accounts. This gets run 4 times a day and the backup target is an NFS share elsewhere.

This is on top of daily backuppc backups of critical folders, automated Proxmox snapshots for docker hosts every 20 minutes, daily VM backups via Proxmox Backup Server and replication to another PBS at home.

I also try and use S3 where possible (seafile and lemmy are the 2 main uses) which is hosted in a container on a Synology RS2423RP+. Synology HyperBackup then performs a backup overnight to the Synology RS822+ I have at home.

Years ago I fucked up, didn't have backups, and lost all the photos of my sons early years. Backups are super important.

Its embassy in Madrid accused him of "demonizing" Israel, saying Spain was "on the wrong side of history."

Israel are confused.

I'm sure they taste great, but my mind is seeing the science class at college with a shelf full of dead small animals in jars.

Lol says the "reddthat" user. Actually it's a good instance name, but the irony ...

Really?! Okay. I think your troll radar is well off, but it's your opinion so you do you I suppose.

Maybe you are the troll. Like 4D chess level of troll. =D

Your post history and mod logs are also quite weird.

Lol what does that mean

The article unfortunately isn't much better when read in it's entirety. A unique identifier is sent along with an encrypted payload. The entire set is then encrypted again in transit. But the author claims the identifier is sent "cleartext".

This coupled with repeated "russian bad" comments peppered throughout. Article is bad.