[diath]

It's actually wild that they're trying to sell lack of basic desktop features as "security features". Try explaining to an average person that when they are playing a game and want to capture a cool moment to share on Discord with their friends that by design the window server they are using will not let them do that and it's "for their own good". Like God forbid I want my computer to be actually usable. We had the same situation in the past when Wayland lacked a way to lock in the cursor within a window and it took them like 8 years to develop a "protocol" or whatever they call it. Imagine that for each basic desktop usability/UX feature, we will have to wait another decade. At that rate Linux will never have widespread adoption on desktop. Wayland sometimes feels like an active effort to sabotage Linux on desktop.

[w4rh4wk5]

I'd say it's completely irresponsible to not have such features, claiming it's about security, rather than implementing it behind a permission system that puts the end-user in charge.

[StopDisinfo910]

It is implemented behind a permission system. KScreenshot works perfectly fine and so will most of the applications using PipeWire I guess, same that screen captures.

KDE is merely saying that some applications will have to be updated to use it so all of the current screenshot applications won't work out of the box.

No idea of why some commenters here are implying screenshots don't work in Wayland. It seems their knowledge is somehow stuck at the first proof of concept ten years ago.

[w4rh4wk5]

I was talking in general. It's less about screenshots and screen recording, but more about drag-and-drop and global hotkeys like push-to-talk in Discord.

[StopDisinfo910]

Screen recording like screen sharing works perfectly fine with PipeWire.

Global hotkeys are also supported perfectly fine. Applications just need to register with the compositor, which will transfer the key press to them. That's the feature working at it should. It prevents applications from hijacking keys when that's not what you want.

The issue is that Discord takes ages to ship anything on Linux and barely supports anything and the Linux community does it's best to keep supporting everything. Other plateformes would have just mandated the new way ages ago and be done with the transition by now.

[hakfoo]

Wayland had the same odor a failed state has.

It's a huge hairball with no easy fixes, but at the same time, that's of significant benefit to some specific players. You can have a very usable X11 desktop with positively pre-Cambrian software. But to keep up with Wayland's ever evolving omnishambles, you basically have to run KDE or GNOME, or maybe Sway.

[ahartmetz]

That is not what the protocol is like at all. Wayland can't do certain things not because they are difficult to do, but because Wayland was initially pathologically minimalist (I say that as somebody who generally likes minimalism) and the approval process for extensions has only improved slowly over time. It turns out that there's much more than blitting rectangles to a (single) screen and routing input events to a desktop environment.

If all the expected stuff was there, Sway (chosen because it's not tied to a desktop environmen) could be your X server equivalent.

[Zardoz84]

I'm using KDE with Wayland and I don't have problems to make screenshots or capture video.

[Jonnax]

I searched online and found articles from December 2024 that Discord supports Wayland screen and audio sharing.

[hulitu]

> It's actually wild that they're trying to sell lack of basic desktop features as "security features".

They copied from the masters: Google and Microsoft. Gone are the days when KDE was years before Windows.