For me it's too much time investment, I don't want to tinker with my OS. The fact that it's so common to screw up a system that atomic distros are becoming much more popular is a good example, I want an OS that doesn't get screwed up in the first place.
It feels like the general consensus is VPN=malicious rather than "VPN=“this guy is just trying to protect his privacy”.
VPNs are used for malicious purposes. After all if a VPN keeps no logs, doesn't track usage, and lets one pay with alternate currency, why wouldn't someone use one if they were wanting to commit a crime?
For any service it's a battle between avoiding blocking actual users, and keeping out the bots and malicious users.
A VPN with a paid dedicated IP may help, or a DIY VPN hosted on a VPS somewhere, but I'd argue it's not really any better than just using your ISP at that point since all your traffic comes from your own unique VPN IP.
Docker is universal, you can easily migrate to any system. If you migrate you're stuck on TrueNAS.
Also you can use watchtower for auto updates with major version pinning when needed (ie; postgres), or one of the many docker images that notify you when updates are available.
For example someone at say, NPR, could use a name like @bob.npr.org which is only possible by verifying ownership of the npr.org domain name, so there is no need to vet anything.
Nah, eggs are fairly easy to replace for baking and stuff, and for cooking there are plenty of other options for protein like tofu or beans
one 16-ounce carton of Just Egg, the equivalent of about 10 small eggs, costs $7.89.
This is also far too expensive to consider when large eggs from local farms are like $5/dozen. And even compared to $8/dozen in store it's still more expensive.
I just use the built in Komodo update checkbox for each stack. No extra config needed, and for things like postgres that don't do major version updates very well I pin the major version in the tag.
The service will always be on a port, that's just how networking works.
Do you mean you want to get rid of the path and serve it on the root or a subdomain? So
https://searx.mydomain/
instead ofhttps://mydomain/searx/