Mike Wooskey

MTLS is great protection, but the use case must support it. For example, if you want your app to support registration for new accounts or if you have a lot of people you want to have access, that might make mTLS unwieldy to manage.

I host apps behind Traefik reverse proxy, using the d.rymcg.tech framework. It make it easy to protect your apps behind HTTP basic auth, Oauth2, or mTLS(or any combination).

AGPL-3. 0. Meh.

I haven’t had to adjust or look at my invidious instance configs in a long time, but I do remember that in their docker instructions and I think I configured my container to restart hourly (or maybe I made it every other hour? Daily?). I’ve had no problems with my invidious instance in a long time, but that may have nothing to do with frequent restarts.

I have aPBS server and my friend in a different geographic region has one. I backup to mine and he backs up to his. Mine syncs my backups to a data so l store in his, and his summer backups to a data store in mine. These are our offsite backups.

To be clear, we’re syncing our proxmox VM backups. But Proxmox Backup Server also has a client app, so I also back up my workstation to my PBS and it also syncs to the remote PBS.

It’s important to me to use devices and services that are local only, but I could only find such robot mowers that are beyond my skillset to build. I have no interest in building and 3d printing and flashing firmware, etc. I just want to buy a device and use it, without my privacy being sold. I’m willing to pay, but I guess there’s not enough market for anyone to build/sell that.

Same with vacuums, by the way. I have a dreametech model that’s supported by Valetudo, but the instructions to flash it sounded difficult and risky enough that I just use it as is, with my home map (and whatever other data it gleans) going through Dreametech’s servers and being sold to whomever.

Sad.