Things like taking screenshots and setting wallpaper actually do have a standard API. That stuff is just part of xdg desktop portals and not the core Wayland protocols. If, for example, a screenshot app uses the org.freedesktop.portal.Screenshot API then it should work with any compositor (as long as the compositor follows the API standards).
If you are familiar with the concepts and are looking more for the specific details, you can probably go a long way with official docs (iptables, nftables, kernel), the arch wiki, man pages, and some hands-on.
Syncthing is another good cloud-free option.
After creating it with mkpart, are you formatting it with mkfs.btrfs? You need to both steps (create partition and format it). Also, try running partprobe or rebooting after making changes so that the kernel re-detects it.
There is a filesystem type field in the partition table. Formatting the partition won’t change it. Delete the partition and recreate it with the correct filesystem type. In parted you can do that with “mkpartfs”.
On the flip side, if 3D graphics performance is not a priority then Intel graphics is incredibly well supported and is probably the most consistently reliable and bug-free graphics option.
Yes, I agree - using a VPN that supports IPv6 is preferred. If they don’t want to/can’t change providers, then disabling IPv6 is the best way to prevent IPv6 leaks without negatively affecting network performance.
In this case, disabling IPv6 is actually the right move. If the VPN provider doesn’t support IPv6, then there’s no way to allow to allow IPv6 Internet traffic without causing a leak/VPN bypass. If you block IPv6 via firewall or routing it to a dead-end, it will add delays as things try IPv6, timeout, and fall back to IPv4. If you just remove the IPv6 address from the Internet interface, you have to also make sure it doesn’t get re-added by SLAAC/DHCPv6 or other interface changes (switching wifi networks, etc). As dumb as it seems, disabling IPv6 or switching to a provider that supports it are probably the best options.
You can move the Z end stop switch up. This will make the home (z=0) position higher.
In addition to the other things mentioned, check the health of your drive. This could be a symptom of corruption.
1Gb EFI, rest of the disk LUKS with a single BTRFS inside. Use BTRFS subvols to divide things up. Swap as a swap file on BTRFS (be sure to set it as no_cow).
What are you comparing it to? I’m pretty sure vnstat is using the raw.interface counters. This would include all protocol overhead. I would expect it to be higher than, for example, an application level counter.