I don’t know what TTY7 is, but if I had to guess I’d say Plymouth, which is the graphical loading screen that covers the boot messages.

SDDM is the login screen, but when you’re already logged in it’s not going to display anything. If you reboot your computer SDDM is what you see before you start KDE. If you use Gnome then this will be different because Gnome doesn’t use SDDM.

The shark kill count would go up way more if we started milking them on an industrial scale.

For comparison here’s the error message KDE displays in the same situation: https://www.reddit.com/r/kde/comments/15477a5/screen_locker_is_broken/

I believe it has no localization support, but the language is clearer and the command it tells you to run is much simpler. A big problem with it is that Ctrl-Alt-F2 does not actually get you to a working TTY on many distros – e.g. on Fedora TTY1 is SDDM and TTY2 is the DE – and the error message is not adjusted based on which TTY is which.

“The empire?” LOL I urge you to look at the TLD of my home instance. The only imperialism here is from the terrorist whose propaganda you posted.

Source: a terrorist

My understanding is that it is fixable by just implementing a couple of APIs, but Artix barely has the resources to fix their own init system, so they aren’t able to support such compatibility.

No you haven’t. The security is the Jellyfin login prompt, then Jellyfin itself, then the Jellyfin container, and if you’re really paranoid, that container won’t be in your LAN.

The funny part is that I can’t tell whether you’re talking about LLMs or the C-suite.