

I totally didn’t use Apple’s permission system to disable (not crowd strike, something similar) because it was breaking everything. In my hypothetical defense, everyone said that rollout was a disaster.
I totally didn’t use Apple’s permission system to disable (not crowd strike, something similar) because it was breaking everything. In my hypothetical defense, everyone said that rollout was a disaster.
dynamic SQL. I remember those days. I once got criticized by colleagues for “breaking” a dynamic SQL search query - you know the one - because I realized that it wasn’t building most of the query. I have no idea how it worked, but I made it put out actually valid SQL and it took forever. I forget if we rolled that back. We were using MS TFS, so probably not haha
You can find that in the ancient artifacts museum, right?
in addition to the other suggestions of checking the rame stick, do you have resource limits on your containers? It’s generally a good thing to have anyway, but I’d do that after checking the ram and cooling situation. Check your cpu temps as well.
I recently switched my home to using cloudaflare tunnels from dns because the ISP blocked traffic. my services are exposed to the Internet, so if you only want access by vpn, I’ve found tailscale to be easier than wireguard. If you want external access, you can get a domain name from CF and set up cloudflared on the host device and target the docker service names. But with both ways, you can have your ports not exposed to the Internet.
I formerly used external DNS until the ISP blocked the modem.
They’re crawling the web, the don’t need to target the fediverse specifically. The crawler will come here and it will either having programming or recognition of sites that update.
the ISP blocked my ports and cloudflare got me around it. I’ll accept the compromise ;)
omg i never picked up on that