4 ms·

It means I can't use Talon for voice commands, and subsequently, Cursorless to voice control VSCode.

ta988 3y ago
This is current requirements for Talon in Wayland https://github.com/splondike/wayland-accessibility-notes/blob/main/talon-requirements.md https://github.com/splondike/wayland-accessibility-notes/blo... Getting there but they need a bit of help if anyone is looking to contribute to an accessibility project.
- ForkMeOnTinder 3y ago
  As a light Talon+Cursorless user, I'd be happy with a very small subset of these features. I'm guessing all you really need for Cursorless to work is 02 (Get PID associated with a given window) and 18 (Emulate pressing keyboard keys). And emulating keys could be done completely outside of wayland, using uinput instead. How can we contribute? When I first started using Cursorless I wanted to try porting the keyboard emulation to uinput before I realized Talon was closed source.
superkuh 3y ago
It means I can't use synergy or barrier or inputleap to use one mouse/keyboard to control all 3 of my desktop computers in the shared monitor span.
- arghwhat 3y ago
  https://github.com/r-c-f/waynergy https://github.com/r-c-f/waynergy, and inputleap seems to have libei support which makes it compatible with some Wayland display servers. barrier has been unmaintained for a long time.
  - superkuh 3y ago
    >barrier has been unmaintained for a long time. As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 10.04 to latest arch. You can't get a waynergy or inputleap to compile on an OS more than 3 years old. And even then, as you say, it's crapshoot if the particular wayland you use will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378 https://github.com/swaywm/wlroots/issues/2378
    - arghwhat 3y ago
      An unmaintained network service written in an unsafe language is generally speaking unsafe to use, and a great way to get exposed to RCEs. You do you, but running such code is a Very Bad Idea™ and absolutely not okay on a normal desktop install. The aforementioned waynergy is a synergy client with explicit support for wlroots-based compositors like swaym.
      - deleted 3y ago
        [deleted]
      - superkuh 3y ago
        Vague insinuations without support, most of which are effectively mitigated by running synergy or barrier over an ssh tunnel. What you mean by "unsafe language"? > waynergy is a synergy client Yes, a client, but you can't actually be a synergy server with waynergy. And input-leap support to work with a subset of the waylands depends on libei.
        arghwhat 3y ago
        "Vague insinuations"? There's nothing vague about it. An unmaintained network server is not safe to run, period. That's not a controversial statement, just common sense from observing how fast we go through CVE's. Can you take steps to reduce risk? Sure, but managing to safely detonate a bomb does not make bomb explosions safe. Suggesting that such unsafe practices can or should be part of a normal desktop setup as you did is definitely not sound.

This is current requirements for Talon in Wayland https://github.com/splondike/wayland-accessibility-notes/blob/main/talon-requirements.md https://github.com/splondike/wayland-accessibility-notes/blo... Getting there but they need a bit of help if anyone is looking to contribute to an accessibility project.

ForkMeOnTinder 3y ago
As a light Talon+Cursorless user, I'd be happy with a very small subset of these features. I'm guessing all you really need for Cursorless to work is 02 (Get PID associated with a given window) and 18 (Emulate pressing keyboard keys). And emulating keys could be done completely outside of wayland, using uinput instead. How can we contribute? When I first started using Cursorless I wanted to try porting the keyboard emulation to uinput before I realized Talon was closed source.

superkuh 3y ago

It means I can't use synergy or barrier or inputleap to use one mouse/keyboard to control all 3 of my desktop computers in the shared monitor span.

arghwhat 3y ago
https://github.com/r-c-f/waynergy https://github.com/r-c-f/waynergy, and inputleap seems to have libei support which makes it compatible with some Wayland display servers. barrier has been unmaintained for a long time.
- superkuh 3y ago
  >barrier has been unmaintained for a long time. As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 10.04 to latest arch. You can't get a waynergy or inputleap to compile on an OS more than 3 years old. And even then, as you say, it's crapshoot if the particular wayland you use will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378 https://github.com/swaywm/wlroots/issues/2378
  - arghwhat 3y ago
    An unmaintained network service written in an unsafe language is generally speaking unsafe to use, and a great way to get exposed to RCEs. You do you, but running such code is a Very Bad Idea™ and absolutely not okay on a normal desktop install. The aforementioned waynergy is a synergy client with explicit support for wlroots-based compositors like swaym.
    - deleted 3y ago
      [deleted]
    - superkuh 3y ago
      Vague insinuations without support, most of which are effectively mitigated by running synergy or barrier over an ssh tunnel. What you mean by "unsafe language"? > waynergy is a synergy client Yes, a client, but you can't actually be a synergy server with waynergy. And input-leap support to work with a subset of the waylands depends on libei.
      - arghwhat 3y ago
        "Vague insinuations"? There's nothing vague about it. An unmaintained network server is not safe to run, period. That's not a controversial statement, just common sense from observing how fast we go through CVE's. Can you take steps to reduce risk? Sure, but managing to safely detonate a bomb does not make bomb explosions safe. Suggesting that such unsafe practices can or should be part of a normal desktop setup as you did is definitely not sound.