The JDA is incapable of defining any discrimination against non-jewish people as antisemitism because it defines antisemitism as discrimination “of Jews as Jews”. In Nazi-Germany thousands of non-jewish people were prosecuted and killed because the Nazis just claimed that they were Jewish, something that would not be antisemitism according to the JDA.

Why didn’t they benchmark ZFS?

“Cloud IDE” - what the fuck?

Haha, point of absurdity, c’mon. SteamOS is Linux, period.

What? SteamOS is (Arch) Linux.

I’d argue most optimizations are negligible. Just install any distro and the necessary drivers and software and you’re good to go.
I did a kernel benchmark once and the improvement of FPS are within margin of error.

If you can’t type a twelve word passphrase, nobody can help you…

Doesn’t seem to be open source.

No loss.

“Journalists flock to yet another proprietary, commercial platform as the last becomes increasingly ‘toxic’ for reasons unknown.”

After changing the MTU to 1200 I have no timeouts anymore, but a lot of read ECONNRESET errors. -.-

I just changed the Docker’s MTU to 1200 and will observe the change.

So the MTU of Tailscale is actually 1280, but is the connection even going through the VPN or rather through my VPS, when Uptime-Kuma is trying to connect to my local domain?

Thanks, since I access my home network and server through the public IPv4 of a VPS via Tailscale this could actually be the issue. I’ll look into it, when I find the time.

Not sure how this helps, but here you go.

Yeah, I suspect it’s simply an issue on the side of DuckDNS. :/

Yeah, it works fine through my browser. Sometimes the websites load a little longer. I feel like it’s an issue with DuckDNS as it’s seemingly random when it works and when not.

IPv6 doesn’t work:

docker exec -it Uptime-Kuma curl -6 proxmox.datenprolet.duckdns.org
curl: (6) Could not resolve host: proxmox.datenprolet.duckdns.org

Besides that the issue has disappeares since last night. I automatically restart all containers at night and moved from uptime-kuma:1 to uptime-kuma:latest. That shouldn’t make a difference, but maybe it did?

And it’s not a typo in my config, but in my post. But good catch. ;)

It’s HTTPS, what else should it be, when I monitor a domain?

What do you mean by tracker? I’m monitoring local domains, that point to local services and their respective web interfaces like Proxmox or Nextcloud. The local domains have a wildcard SSL certificate via DuckDNS.