3 ms·

How do accessibility tools work with that? They need to examine and control other running processes.

• stop50 1y ago
  Fake inputs are done with uinput(kernel interface). Access to the screen is usually over pipewire.
  • panzi 1y ago
    Doesn't writing to /dev/uinput require you to be root? That's way worse security wise than faking X11 inputs. Also you can't direct the inputs to a specific window. That is bound to create problems where events go to the wrong process. Also PipeWire is an audio interface. A replacement to PulseAudio. That has nothing to do with accessing screens.
    • yjftsjthsd-h 1y ago
      > Also PipeWire is an audio interface. A replacement to PulseAudio. That has nothing to do with accessing screens. No, it's a general audio/video system, including video from cameras and virtual video streams from screen capture; see https://wiki.archlinux.org/title/PipeWire#WebRTC_screen_sharing https://wiki.archlinux.org/title/PipeWire#WebRTC_screen_shar... for some discussion.
      • panzi 1y ago
        Didn't know it also does video. But accessibility tools don't just want video, they want APIs to read all text and other GUI structures directly. OCR is just too imprecise and a waste of resources.