featured [he/him, comrade/them]

Reenable the firewall with

systemctl start firewalld 

Then get the current networking zone with

firewall-cmd —get-active-zones 

It will likely be called FedoraWorkstation, if not just replace that name with whatever it is called in the following steps.

Next you should enable the ports for Moonlight, which from a quick ddg search I think this should do it:

firewall-cmd —zone=FedoraWorkstation —permanent —add-port=47998/udp

firewall-cmd —zone=FedoraWorkstation —permanent —add-port=47999/udp

firewall-cmd —zone=FedoraWorkstation —permanent —add-port=48000/udp

firewall-cmd —zone=FedoraWorkstation —permanent —add-port=47984/tcp

firewall-cmd —zone=FedoraWorkstation —permanent —add-port=47989/tcp

firewall-cmd —zone=FedoraWorkstation —permanent —add-port=48010/tcp

firewall-cmd —zone=FedoraWorkstation —permanent —add-port=47990/tcp

Then reload the firewall with:

firewall-cmd —reload

Lmk if that works

Edit: added more ports needed for the WebUI and controller support. Check the docs here if you wanna see what each port is used for

I use Graphene on my phone and DivestOS on my tablet

Worth noting that on Fedora this is true, UNLESS you use the proprietary nvidia drivers. Then no secure boot

It is but they’ve been making huge leaps towards a Linux build and that’s what this is about

Linux NTFS support is pretty good. The kernel drivers do all the basics, but you may still want the ntfs-3g driver installed for some of its tools. Ntfsfix has saved me before and I think it’s from the ntfs-3g package

Instead of installing packages through a package manager one at a time and configuring your system by digging into individual config files, NixOS has you write a single config file with all your settings and programs declared. This lets you more easily configure your system and have a completely reproducible system by just copying your nix files to another nixos machine and rebuilding.

It’s also an immutable distribution, so the base system files are only modified when rebuilding the whole system from your config, but during runtime it’s read only for security and stability.

I just recently moved my home server from truenas to RHEL. I already use Fedora on my laptop and the enterprise Linux space has incredible support. Something like Rocky could be perfect for you if you value stability and long term support

You can enable compact spacing in about:config

I like KDE’s conformance to open standards, which is better than GNOME’s, and pace of development. However you’re absolutely right that the UI on KDE is inconsistent, messy, and buggy as hell. GNOME is still my go to because it’s just so polished, but I’m looking forward to COSMIC this year for that nice tiling workflow

X11 is the traditional most popular display server for Linux and other *nix systems. However it is very dated and has a lot of flaws, including endless spaghetti code that makes maintenance a nightmare, huge security holes where any application can freely scrape information from any other, and tons of bugs dating back decades. It isn’t sustainable to keep developing on X11 as a platform because it is so flawed and devs hate working on it when implementing new features or fixes.

Wayland is a modern protocol for display server/compositing tasks which seeks to directly address all of the major issues of X11. It is small and modular, with purpose driven portals and protocols written to interact with a simple core, rather than being monolithic and opaque like X11s code structure. It is security focused, with the aforementioned portals used to grant permissions to applications when needed but nothing more. Wayland has a more efficient pipeline resulting in better performance. It is overall a pleasure to work on comparatively and is a much richer, progress oriented protocol than X

Why are you hearing about it now? Because Wayland is finally mature enough to warrant almost everybody to stop using X11. There are a few features that are still not present in Wayland that should be for particular use cases, but these are exceptions nowadays. Applications are starting to prioritize Wayland compatibility, distros have overwhelmingly made the switch to it as default, and most Linux display server developers have moved away from X and onto Wayland. It seems that the transition is nearly complete but the last hurdles have certainly been creating lots of discussion