that doesn’t rely on kernel features

You know that “until Wayland is polished enough” is at least a year ago for the overwhelming majority of people, right?

It means that the display I stream doesn’t show on a physical stream. When the stream start, it can automatically be set to the resolution and framerate of the client.

This is especially useful when the client has a resolution and/or refresh rate not supported by a connected physical screen. For example, I always used to have vertical black bars on my phone because it is so wide, and horizontal ones on my Surface because it is so square, but not anymore.

It also means I coult setup multi-seat stuff and keep using my pc while someone else is streaming.

Sway, it’s fast, pretty, easy to customize, and can do headless displays to stream with Sunshine.

So you think NONE of the software you use will ever get an exploit? “Not do anything dumb” only covers some threats, not all.

Wow I’d reguster for that right away 😉

Compressor is bad, normalise is good

Prédio - Apanhador Só

Is it in the Debian repos? Also I hope it doesn’t need anything newer that SSE2 on the CPU, so far that has been one of the biggest blockers for running some programs on it.

Same, I have memories of playing AoE2 as a kid on it, and eventually even AoE3 as a less-kid

Yeah it’s an old swap partition that I never touched on the drive when repartitioning. No idea what I was thinking when I created it! To be fair I must have been 15 years old at the tine.

Ok fair, but I still think that “a few bugs that make it not act like i3” is quite different from “doesn’t have backwards compat with i3 right”.

None of those bugs affect me, so I can see why my perspective of Sway being perfectly usable may differ from other users whose workflow is broken.

Looking forward to Sway having fifo, seems to work well in KDE and Gnome

So don’t use Sway, plenty of DEs are more polished.

Most of the bugs you linked to are not related to Nvidia or the post. I don’t know who is suprised thay Sway, which is relatively new, has unresolved bugs that i3, which is older, does not have.

Definitely not all of the Nvidia users, since I am one, and have no issues at all. I am even on an “unsupported” configuration, since I use Sway and they don’t officially support Nvidia.

Wayland does not suck on 60% of graphics cards. No need to spread misinformation

They are probably running a system full of “workaround” environment variables that are not needed anymore or something like that, and seeing issues because of it.

I’ve also had a flawless experience with Nvidia & Wayland recently.

For actually using the machine I would go with another Fedora Atomic distribution, such as Sway, or the XFCE or LXQt Fedora Desktops.

Appart from being a bit slow because of full fat Gnome it was very nice and usable.

Also I thought broadcasts only went to connected devices. Aka having a big subnet with 20 devices will have the same performance as a tiny subnet with 20 devices. Does the size of the subnet really make a difference, or is it only the number of actual devices?

I didn’t know there was a performance penalty to having big subnets. I’ll have to look it up and shrink them.

But this is relatively moot since all my devices talk via ipv6 now. The only thing without ipv6 support I have is Mikrotik devices that only expose their management interfaces over ipv4. Anyway these are only in one VLAN, the management one.

Ah I misspoke. I have different VLANs, not just subnets. So nothing really goes through layer 3 to talk across subnets, as nothing is allowed to go from one VLAN to another. I use them to split the networks between devices that should not talk to each other.

Then I can have fun stuff like 10.42.0.X are static IPs for known devices, and 10.42.1.X is DHCP addresses for unknown devices. This is also only one subnet, I have quite a few for management, IoT stuff, guest network, work devices.

Anyway my network is ipv6 now. Sadly fastfetch doesn’t show it, though I’d have to censor it to avoid doxxing my prefix.