Better than that, the lack of reliance on spinning disks means that asset duplication and data read order is less of a requirement to reduce load times. It can still be argued that there’s just too many polygons, since simply scaling things back would be plenty effective in reducing storage usage and load times.

Because you’re serving the website on a non-standard port, you will always need to provide the port in the web browser.

That said, I don’t see anything wrong here. It looks like you’ve got the right ports set, TCP should be correct. You may not get a ping, because ICMP is likely not enabled at the modem. When you ping, you ping the first device that’s exposed to the internet, not an open server.

Just to be sure, when you’re on your phone, you’re using data? If you’re on wi-fi, the modem/router may not be configured to perform NAT reflection, so you won’t be able to access anything via your WAN IP.

Non, Dora s’appelle Dora en anglais. The meme is just weird.

Can’t speak for them, but it’s very useful for interfacing with any number of smart watches/scales and more with on-device data storage. It doesn’t always support things perfectly, but it’s definitely good enough to prevent a need for manufactuer specific apps for the devices it does support.

If I’m remembering right, RHEL is Crowdstrike’s primary Linux target. And NixOS wouldn’t even be a factor since it’s basically just not enterprise grade.

That said, they need a serious revision of their QA processes.