Re:Understanding the working of X11 from the ground up (2017)
by yjftsjthsd-h on Sunday September 22, 2019 @02:35AM
(#21039996)
From my perspective, Wayland "fixes" things that could allow bad things but were also useful. For instance, screenshots/recording took a long time to be implemented, and is still constrained, because of the security risk of arbitrary programs recording the screen. Because that is a risk... but users still want it. As another example, I use xdotool to inject input to programs in X; in Wayland, that would need to be explicitly supported per-compositer.
[ Parent
| on HN ]
Re:Understanding the working of X11 from the ground up (2017)
by zzzcpan on Sunday September 22, 2019 @08:59AM
(#21041159)
Well, removing or not implementing such features because of security is always a big fat sign of something sneaky or even worse, outright incompetent going on. As such security risks of features can always be addressed through some sort of authorization mechanism.
Re:Understanding the working of X11 from the ground up (2017)
by shmerl on Sunday September 22, 2019 @02:47AM
(#21040023)
Instead of xdotool, you can use this: https://github.com/ReimuNotMoe/ydotool
Re:Understanding the working of X11 from the ground up (2017)
by dyanaraps on Sunday September 22, 2019 @03:26AM
(#21040103)
Not exactly a 1:1 replacement though:
> This program requires access to /dev/uinput. This usually requires root permissions.
Source: https://github.com/ReimuNotMoe/ydotool#runtime
Edit: I'll also add that only 5~ commands have been implemented so far in ydotool.