If it makes you feel any better, with the age of these two candidates and the speed of the courts it’s likely that it didn’t actually matter before the ruling. They’re not exactly consequences if they happen after you’ve died peacefully of old age.
If it makes you feel any better, with the age of these two candidates and the speed of the courts it’s likely that it didn’t actually matter before the ruling. They’re not exactly consequences if they happen after you’ve died peacefully of old age.
That’s like some magic spell or something. Being the president for a few months, while you actually spend most of your time campaigning, can not possibly make someone that much more electable.
Yeah, and I assume future me will be even dumber than present day me, so I try to make it really easy for him to find out what he needs to know.
Another good tip is to put timestamps and increase the length of your bash history. That way when I log in half a year from now I’ll know what I was up to.
All of your issues can be solved by a backup. My host went out of business. I set up a new server, pulled my backups, and was up and running in less than an hour.
I’d recommend docker compose. Each service gets its own folder inside your docker folder. All volumes are a folder in the services folder. Each night, run a script that stops all of them, starts duplicati, backs up to a remote server or webdav share or whatever, and then starts them back up again. If you want to be extra safe, back up to two locations. It’s not that complicated if it’s just your own services.
There’s no forgetting where I have something hosted. If I ssh to service.domain.tld I’m on the right server. My services are all in docker compose. All in a ~/docker/service folder, that contains all the volumes for the service. If there’s anything that needed doing, like setting up a docker network or adding a user in the cli, I have a readme file in the service’s root directory. If I need to remember literally anything about the server or service, there’s an appropriately named text file in the directory I would be in when I need to remember it.
If you just want a diagram or something, there are plenty of services online that will generate one in ASCII for you so you can make yourself a nice “network topology” readme to drop in your servers’ home directory.
Landlords are familiar with utility install people and how unpredictable they can be. Even if they get mad, this will put the blame squarely on someone else so it’s probably a good option for you. “I dunno why he put it there. You know how utility guys are. It’s the only place he’d put my hookup.”
Second this. Landlords don’t want their stuff screwed up by inexperienced tenants’ diy projects, and they don’t want to pay for something they think it’s unnecessary. I’d get an estimate for a pro to do it (could be a guy off Craigslist or whatever, just someone who does this for a living) and then just ask the landlord if they’d be alright with you paying to get it done. They’ll probably want to know exactly what they’re going to do, and they’ll likely say yes, especially since you say they already have coax running through the house.
Wireguard with systemd is even better. You set it up and then literally never touch it again.
They’re less lethal, not non lethal, and they’re frequently used as an excuse to escalate violence needlessly. I’m very critical of the use of their use of force and would generally prefer police to be unarmed, but this is not a situation where I have any complaints. That threat needed to be neutralized as quickly and effectively as possible. Overwhelming force was the best way to do that.