Well, instead of stealing from the drivers, to give to a corporation, it steals from tourists to give to drivers. I say it's not good but it's still less bad

Yeah, we are a bureaucracy machine.

People (especially us) often make fun of how convoluted our bureaucracy is, but this has made us extremely good at paper moving. If any country had a go at being us, they would collapse.

Italy. Because you need a license to be a taxi driver, and a random company cannot hand them out (and the taxi drivers union is powerful and corrupt). And because the government gotta know who is renting a room where, you can't just go wherever you want without anyone knowing, especially foreigners. Whenever you rent a room in Italy, the owner will take a picture of your ID/passport, and send your data to the local government. Also you gotta pay taxes on the rooms you rent.

It doesn't have to be like this though.

Here, for example, Uber is not allowed and Airbnbs are regulated

Short side because it's TV facing (in my living room). Edge seat because I like the arm rest. It would be even better If the arm rest was to the right, but my sofa is a reverse L.

Don't use a raspberry pi.

RPI5 only has h265 decoding, everithing else is handled by the cpu. Which is fine for 1080 as long as that's all the sbc is doing, but if you are also running some server, or you want anything h264 above 1080 you are out of luck.

RPI4 should be a little better, it has h264 and h265, don't know the supported resolutions/framerates, but the cpu is considerably less powerful. Also, the cpu lacks encryption acceleration, so if your are getting your movies over https that's gonna take a toll.

Older Pis are goint to be unsupported by kodi and jellyfin, so don't get those.

None of these is a dead no-go, listen to other peoples experiences. But I personally would advise against any Raspberry Pi. Maybe and Orange Pi is better? I don't know. My suggestion is to avoid the SBC, and get a cheap second hand Intel pc instead (possibly a very low power one). Intel's quicksynk video accelerator is gonna run laps around any sbc at any resolution, and it's gonna support more decoders, and even some encoders if you want to run transcoding in a jellyfin server.

Edit: If intel sold a quicksink pcie card, I would put one in my rpi5. But it don't.

Edit 2: I should add that some streaming services block 4k on Linux

If it's a Wayland application it will support global shortcuts.

For X11 apps. If you are on KDE there's this menu:

Other DEs have different ways to deal with this.

And if you are on Gnome, change DE. Gnome will always follow its own philosophy, because apparently it doesn't align with yours, you should use something else.

Btw, I gave the same answer in the previous comment.

Also, on the "how can you consider this polished"... Wayland supports global shortcuts, this is a fact. What it doesn't support is "global shortcuts for apps that use a protocol that is not Wayland". I think I made my point

https://github.com/X11Libre/xserver/pull/56

Here is the x11libre dev not understanding what the ^ operand does in C. Would you trust running this person's code as a display server?

Sure. No one expects anyone to know everything from the start, and people improve with time. But this was metux's understanding of C when he forked off xorg thinking he could do better than freedesktop.

That is a feature. Allowing arbitrary programs to read any key press is how you get keyloggers.

Wayland has a protocol to request reading keys out of focus (which will ask the user for permission, as opposed to just read it like on xorg).

If the program was running in xwayland (which it probably was) of course it won't use that protocol, and will just try to read it X11 style.

In some DEs (KDE) you can select if X11 apps are allowed to read keys.

"I switched to X11 and it immediately works". I'll give you another tip: if you run chmod 777 -R / the file manager stops pestering about permissions and it immediately works.

Test better.

• Discord works
• Teams works
• OBS works
• Sunshine works like a charm
• Built-in VNC/RDP servers work
• I think zoom also works

Of course you can expect things with names like "Xultra-Xold-Xscreen-Xsharing-Xtool-11" to not work. Trying any of those and complaining it doesn't work is just disingenuous and facetious.

Edit: I forgot you had a real question after the misinformation. Here's some things Wayland does better

• It supports HDR
• It doesn't tear
• It's by design more efficient
• It's more secure
• It actually support track pads with kinetic scrolling (if you think kinetic scrolling works on X11 it means you don't know how it works)
• To crash the screensaver you need to crash the whole desktop, which means you don't get unauthorized access to it
• It actually supports multiple monitor (with different resolutions, different scales and different refresh rates)
• They just merged actual support for multiple GPUs (xorg doesn't have that)
• It supports explicit sync (xorg supports just enough to run inside Wayland)
• It's supported by Nvidia GPUs (for X11 you need to use Nvidia's closed source bespoke implementation of xorg)

But it's just to name a few, you know...

Uinput and libinput are the proper tools and they both work.

Also, the keyboard configuration is done with xkb

I'd like to chime in on the "average hardware" claim.

The idea that Wayland is more demanding to run than X11 is a misconception.

Mutter (Gnome's compositor) and kwin (KDE's compositor) are more demanding than xorg plus a simple window manager. Usually that's what people used to compare when they said that Wayland is demanding, and now they just keep repeating it.

In actuality, the Wayland protocol is more efficient by nature. So a light Wayland compositor (e.g. labwc) will run better on limited hardware, than a light X11 window manager.

Tho, Wayland requires proper EGL support, which you might not have on some old exotic hardware (e.g. a Tegra 2/3/4 tablet).

The example I usually make is:

• Dig up an old intel atom netbook (it's old and
• Try using regular lxqt on x11
• Now try lxqt on labwc
• See which one you'd rather use