Also bad is that hair dryers don’t spread their heat around very well at all. You can easily create hotspots on the object and damage things with them.

I agree, unfortunately. The only reason I stick with ddg over Google is because, unlike Google, they don’t smother me with captchas the moment I enter a VPN.

Man wait till you hear WhatsApp lets you send messages to yourself

Someone should photoshop that text in the lower right corner to Stargate or something

I also find ORMs and query builders much easier to debug than most mative SQL database queries. Mostly because native SQL error messages tend to be some of the most unhelpful, most undescriptive crap out there, and ORMs help a bit with that.

Seriously, fuck MySQL error messages. 9 times out of 10 shit boils down to “you got some sort of error somewhere roughly over there, go fix”.

I ran into that same DNS issue with pi-hole but in a docker container, and the (bandaid) solution was to put the container in host network mode too. But turns out it’s not an issue but a feature. By default pi-hole only responds to DNS queries from within its local network. The host machine’s LAN is an external network to the containers, unless you set the container’s network mode to host. Pi-hole does have a setting to make it respond to DNS queries from other networks as well, though. What I’m saying is, that might not have been a podman issue.

Something is already listening on port 80 on the pi, which is why your tunnel failed.

Been a while since I set up OMV myself, but does it even use port 80? Doesn’t it expose its web UI on a non-standard port?