I see an em-dash on a comment in MainActivity.kt on line 278, so I’m guessing it was used extensively. Also, a “→” character on 291.

Impossible. Signal said they have no choice but to use AWS for this kind of thing.

I think I’d install proxmox on all machines because there is a proxmox provider for Terraform. Then, manually create the VMs, and to learn the barebones, use kubeadm to set everything up, and kubectl to manage it. Once comfortable and knowledgeable with that, start messing around with Terraform and Ansible.

It’s been a while since I messed with home automation, but ESPHome was amazing to program ESP microcontrollers (i.e. you most likely wouldn’t have to write any code). You can use ESPHome devices with both Home Assistant and Openhab (using MQTT, IIRC). The last I checked, it was easier to program your own functionality in OpenHAB than Home Assistant.

For servers, I usually choose the distro with a version with the EOL scheduled furthest into the future. Usually that means Ubuntu (Server) LTS.

Postgres is basically an open source version of Oracle DB. Much more featureful than MySQL. I believe Oracle bought MySQL just to kill it.

Port forward/poke holes in firewall + dynamic DNS.

I’ve been going down this rabbit hole myself. Already set up a solar Meshtastic node and MeshCore repeater. Kinda cool, very low bandwidth and pretty unreliable though.

It’s my understanding that encryption is illegal on amateur radio bands. I’m thinking about getting a license anyways; looks fun.

HaLow, BATMAN, Reticulum and stuff like that also look cool, but I haven’t messed around with those yet.

I think radio will always have bandwidth/congestion problems. It’s like everyone within range is using the same “wire.”

I also like overlay networks like Tor and I2P, but it’s possible those will eventually be blocked or made illegal in many countries, if governments keep heading in the direction they seem to be heading.

You can boot Pis off an USB HDD or SSD. I think there are specific hats for that as well. But yeah, backups, at least of configs, are nice.

Ain’t broke and I can’t be bothered to update. Not accessible publicly either. It also runs some software with very specific and brittle dependencies and I don’t care to risk breaking it. If distro is EOL (probably is) then it’d be a pretty time consuming getting everything set up again.

When something doesn’t work. I.e. when an app update causes incompatibility with a service. I think I have one server that’s a few years without an update (distro version may actually be EOL for all I know).

Excessive use of em-dashes, emojis, and other characters that aren’t on standard keyboards. I think these companies purposely have the models generate this stuff so it is easily detectable (so they avoid training on their own slop).

Outside of the “stars” and directors, people working in the film/tv industry already have a fairly low income (median salary for professional actors is ~$47000/yr).

I think compose files are usually pinned to a version, or use a .env file that needs to be changed to update to a new version.

I personally don’t update very often; usually not until I’m forced to for some reason. I find that just checking the documentation for any upgrade/migration guides, and doing it manually is sufficient. I don’t expose this kind of stuff publicly; if I did, I’d probably update regularly.

I had a Mox and it was the most stable router I’ve ever had. Never had to power cycle it, and I even have to power cycle my fancy Asus somewhat often.