BTRFS should be stable in the case of power loss. That is to say, it ought to recover to a valid state. I believe the only unstable modes are RAID 5/6.

I’d recommend BTRFS in RAID1 mode over mdadm RAID1 + ext4. You get checksumming and scrubs to detect drive failures and data corruptions. You also have snapshotting, in case you’re prone to the occasional fat-fingered rm -rf.

For backup, maybe a blu-ray drive? I think you would want something that can withstand the salty environment, and maybe resist water. Thing is, even with BDXL discs, you only get a capacity of 100GiB each, so that’s a lot of disks.

What about an offsite backup? Your media library could live ashore (in a server at a friend’s house). You issue commands from your boat to download media, and then sync those files to your boat when it’s done. If you really need to recover from the backup, have your friend clone a disk and mail it to you.

Do you even need a backup? Would data redundancy be enough? Sure if your boat catches fire and sinks, your movies are gone, but that’s probably the least of your problems. If you just want to make sure that the salt and water doesn’t destroy your data, how about:

1. A multi-disk filesystem which can tolerate at least 1 failure
2. Regular utilities scanning for failure. BTRFS scrubs, for example.
3. Backup fresh disks kept in a salt and water resistant container (original sealed packaging), to swap any failing disk, and replicate data from any good drives remaining.
4. Documentation/practice to perform the aforementioned disk replacement, so you’re not googling manpages at sea.

This would probably be cheapest and have the least complexity.

And the best tutorials are a blurry notepad window while this song plays

A better ending than last time, when Fuzzy-Select Girl tried to stop a gang of superdrug-dealers with an improperly calibrated threshold… Ended up deleting half the neighborhood.

I wouldn’t trust anything like that to the open internet. It would be better to access the system over a VPN when you’re outside the network.

Barony is fun as hell. Engine is FOSS, but the default game assets require purchase.

You’ve laid out one potential development cycle: FOSS from the get-go, and open collaboration welcome.

However, that’s not the only way that a FOSS game might be developed. The code could be freely licensed, but the upstream developers refuse to accept outside patches. In that case, there’s one “original” and then if you don’t like it, build your fork.

Alternatively, a game could be developed entirely in-house under proprietary licenses, and then only made FOSS upon commercial release. Contributor patches could improve the project, but conception of the game would be entirely the domain of its original developers.

The man is a monster. I don’t know how many of my build jobs have been murdered by this fiend.

How about writing a script to automate the deletion, thus minimizing the chance of human error being a factor? It could include checks like “Is this a folder with .git contents? Am I being invoked from /home/username/my_dev_workspace?”

In a real aviation design scenario, they want to minimize the bullshit tasks that take up cognitive load on a pilot so they can focus on actually flying. Your ejector seat example would probably be replaced with an automatic ejection system that’s managed by the flight computer.

Yeah, I believe there’s some kind of bridge mode you must enable on the host’s interface.

As others have said, a reverse proxy is what you need.

However I will also mention that another tool called macvlan exists, if you’re using containers like podman or docker. Setting up a macvlan network for your containers will trick your server into thinking that the ports exposed by your services belong to a different machine, thus letting them use the same ports at the same time. As far as your LAN is concerned, a container on a macvlan network has its own IP, independent of the host’s IP.

Macvlan is worth setting up if you plan to expose some of your services outside your local network, or if you want to run a service on a port that your host is already using (eg: you want a container to act as DNS on port 53, but systemd-resolved is already using it on the host).

You can set up port forwarding at your router to the containers that you want to publicly expose, and any other containers will be inaccessible. Meanwhile with just a reverse proxy, someone could try to send requests to any domain behind it, even if you don’t want to expose it.

My network is set up such that:

• Physical host has one IP address that’s only accessible over lan.
• Containerized web services that I don’t want to expose publicly are behind a reverse proxy container that has its own IP on the macvlan.
• Containerized web services that I do want to expose publicly have a separate reverse proxy container, which gets a different IP on the macvlan.
• Router has ports 80 and 443 forwarding only to the IP address for my public proxy

Did you mean source-available?

I guess? Always thought there was some pedantic Stallman-esque argument for the differentiation between FOSS and OSS, independent of the Open Source vs Source Available distinction.

Not sure if you’re able to edit the title, but this doesn’t look like FOSS, just open source.

It would have to iterate over all saved keys, which sounds rather inefficient to me and potentially unsafe (timing attacks etc.)

sshd only checks for matches in the user’s authorized_keys file, not system wide.

I kinda get “new-age cult” vibes from some of the interior pictures

Also, while I bet the house is quite heat efficient, the underground design means that rooms in the back will get no natural light, which would be pretty miserable.

Ooh! Thanks for the tip! Been looking for some affordable drives for my next system.

I bought a LFF Dell Poweredge back in the fall, and have been waiting on a good deal for 3.5" disks. My current machine is a SFF HP Proliant, and I hate how much a 2.5" drive with good capacity costs.

A bridge in America collapsed after a cargo ship crashed into it.

Checks are still common in the USA. Not so much used by people, but businesses and corporations who transact money with people (eg insurance or banks).

What would happen is:

1. You take the check and cash it (assuming they accept it at all)
2. They find out it’s fake
3. You have to give the money back before Rocco rings your doorbell with a baseball bat in hand

Doesn’t seem worth it to me.

In truth though, they’d never accept the check. 99% of the time, scammers send an image of a check, then ask you to print it and use mobile deposit to put in your account. That way, nobody ever touches it and realizes it’s a shitty jpeg on printer paper. It wouldn’t fool anyone IRL.

Sometimes, they might send an actual check that they stole and doctored up, but that’s too much work for a scammer most of the time.

The scam is not downloading Signal. The scam will come later when they say “You just got the job! I will send you a check to purchase your remote work supplies”.

Do not deposit the check. At all. No matter what. It is not a legitimate check. It will never be a legitimate check. No matter how real the check looks, I guarantee that no company works like this! Do not respond to them. Block their number and ignore them for the rest of your life.

What happens is: The check is fake and you deposit it. By law, your bank is required to credit your account with the check’s value within a couple of days. HOWEVER: Just because your account gets credited the amount, doesn’t mean the check is fully processed. The scammer will tell you to buy WFH supplies from a “trusted vendor”. You are “buying” your supplies from the scammer, using the money credited to your account. Then, in 2-3 weeks, the bank will reject the check as fake. They will subtract the value from your account and you will have paid for your “supplies” using your own money. You will never receive the “supplies” or get your money back. The bank might even suspend your accound because of the fraudulent check.

A youtube channel that I follow actually released a video today about employment scams. In the section where he talks about red flags, compare them to the messages you just received. I bet you’ll notice some similarities. https://www.youtube.com/watch?v=K9g-y8wVzws