ZLUDA originally only supported on Intel since it was designed by an Intel employee, but AMD hired him to make it work for AMD instead. So in a way Intel is somewhat important here.
Although it looks like it's literally just slightly possible to leak the load on the system. It's hard to pull off, and isn't precise enough to leak anything important.
A lot of external status services just send a HTTP request to a certain url, if it succeeds then it's up, if it errors or times out then it's down. They also usually let you check if TCP ports do the usual handshake thing if you aren't using HTTP.
The response time can also be used to check if a site is running slower than usual too, and if you have a use for it you can usually specify the required response code for success.
Although I wouldn't be surprised if GitHub has some per-server analytics they can also use to estimate the load, but Instatus would work as described above.
Sometimes these sorts of things are referred to as health checks, if you're looking for search terms. For example Docker can be set up to poll a container's web server every few minutes, and mark it as unhealthy it if it stops replying using the HEALTHCHECK instruction in the Dockerfile.
I've had a similar issue with a monitor not properly supporting VRR, I ended up dumping the EDID and forcing Linux to use that instead of the monitor's.
Like other people have said, day to day it works with no issues, I'm also running Wayland; but it did struggle with picking up both my monitors' VRR, and I ended up changing random things in the monitor EDID to get it working.
NTFS-3G on Linux is very stable, and I'd recommend sticking to that, although I'd avoid the newer NTFS3 driver.
But if you really want to convert, and it's data that you don't mind loosing, ntfs2btrfs can convert NTFS partitions to BTRFS, and it's available in most distros' repositories.
Nah, apparently it's completely valid to end IPv6 addresses with a 0. And I haven't done much research, but it seems IPv6 really doesn't have network addresses the way IPv4 does.
Actually thinking about this, I believe Tux would only show on kernels newer than 2.6.20, released in 2007, or at least CONFIG_LOGO was. So it seems that kernel is a lot newer than those modules it's loading.
Yeah, here's the original meme: https://lemmy.world/post/12825315