8 ms·
Wayland does not care about security. In fact it does not even offer standardized access control protocols. The flaw here (among many others) is that the protoc
by sprash 4y ago
Wayland does not care about security. In fact it does not even offer standardized access control protocols. The flaw here (among many others) is that the protocol that is responsible for negotiating display output for multiple processes (which is what Wayland tries to be) should also contain standardized interfaces to exchange that output among processes, but Wayland doesn't.
- tadfisher 4y agoNo. Wayland is a display protocol, not a general-purpose IPC, no matter how allergic to DBus you are.
- sprash 4y agoYes. Wayland is a display protocol, not a general-purpose IPC. Hence it must contain access control interfaces for buffers. Only the compositor has access to the composited image therefore is the only program able to make screenshots and full screen sharing. Furthermore, efficient sharing of single application windows is only possible with direct memory access to the buffer which also is something the compositor does/has. The Display protocol is the only sensible place to negotiate access to GPU resources.
- QUrprUd1nCeicw 4y ago>The Display protocol is the only sensible place to negotiate access to GPU resources. No, GPU resources can come from any number of other places. That's literally the purpose of direct rendering. Any applications using GPU compute can produce them without requiring a connection to the display server. There's no reason to put that in Wayland or restrict it to the compositor. There's already a much better protocol for sharing GPU buffers: Pipewire. Dbus is only there to act as the glue between a Wayland compositor and Pipewire.
- sprash 4y ago[flagged]
- QUrprUd1nCeicw 4y agoNo, with direct rendering the display server uses the same API as any other process that uses the GPU. The way to fix stuttering is to fix scheduling in the kernel. XGetImage is comparing apples to oranges. That doesn't use the GPU at all, that does a copy into main memory. Pipewire is complicated because it has to handle format negotiation and conversion and audio support and a lot of other things that make sense for generically transferring video between processes but are outside the scope of the display server. Can you please knock off the conspiracy theories and flames? What are you hoping to accomplish by hurting people like this on the internet?
- sprash 4y ago[flagged]
- tadfisher 4y ago> The whole ecosystem is garbage and is either conceived by complete moronic retards or with the purpose of sabotage. The latter is more likely, nobody can be that stupid. > This exactly the behaviour that I would expect from Wayland apologists, though. Your arguments are obviously wrong and pointless and the best thing you can come up with is shaming other people into self censorship. Yeah, I'm going to shame you for that. That kind of language isn't going to convince anyone, and it's actively harmful. Please stop.
- QUrprUd1nCeicw 4y agoI didn't tell you what to say. I asked you nicely. Notice I used the word "please." You can make all the arguments against Wayland you want. Promoting baseless conspiracy theories and verbal abuse calling other people morons doesn't help get your argument across. It weakens your point. You're just hurting people as well as hurting your own argument by making these comments.
- 4y ago