synergy-core VS ydotool

No one has mentioned ShareMouse yet? (https://www.sharemouse.com/) In my experience it has worked way better than Synergy. I switched after getting fed up with the synergy developers not responding to various multi-year old bugs that made the software unworkable for me (e.g. https://github.com/symless/synergy-core/issues/5992).

The only downside is that you have to "renew maintenance" to continue receiving updates to ShareMouse after a year. But I haven't done that yet and it still works fine for me.

I want to be able to do things like Synergy, Steam Link, Unified Remote, and Media Servers between any of these devices, with as little added latency as possible (especially important for steam link)

i've got several fedora linux machines running and sharing their monitors via synergy (https://symless.com/synergy) , all controlled by the keyboard/mouse on the primary synergy server.

Not sure if this is what you're asking, but I've been using Synergy Pro (Windows, macOS, Linux) for years, and it works seamlessly. It lets you share your mouse and keyboard across multiple systems (with or w/o encryption), copy and paste between computers, etc.

I've got an M2 MacBook Air

Per the Advanced... screen under Displays in System Settings, you can link to a Mac or iPad to control it a la Synergy[0]

I have not done it myself, but I do not see why you could not do it with a current-gen Mac Mini

---------

[0] https://symless.com/synergy

I previously used a software solution to do the same thing and it was actually really good, better even. It might have been this software but I have to check to be sure - https://symless.com/synergy - as I’m not at my laptop right now.

Wayland provides little by design, so this is quite typical. For example:

Screensharing is handled by pipewire [0], changing keyboard layouts aren't defined [1] by wayland, and generally anything Wayland devs think would 'corrupt' their protocol.

They leave most things to the compositor to implement, which leads to significant fragmentation as every compositor implements it differently.

Long gone are the days of xset and xdotool working across nearly every distro due to a common base, now the best you'll get is running a daemon as root to directly access `/dev/uinput` [2] or implementing each compositors accessibility settings (if they have them) as a workaround.

[0] https://superuser.com/questions/1221333/screensharing-under-...

[1] https://unix.stackexchange.com/questions/292868/how-to-custo...

[2] https://github.com/ReimuNotMoe/ydotool

I personally use libinput-gestures to call commands using touchpad gestures. You can also combine it with ydotool to bind macros and such to your gestures, e.g. 4 fingers swipe down closes the current window, 3 fingers swipe left or right changes workspace, etc

Have you tried using the systemd unit file supplied with ydotool? It's probably installed somewhere on your system. Else you can get it here and just change the install location of ydotoold.

For simulated keyboard there are tools such as dotool or ydotool and KeePass extensions such as KPUInput that work by giving the user access to /dev/uinput. That works, but it's a bit inelegant; I guess in the future a Wayland protocol for simulated keyboard input will emerge, like wlroots already has, also for virtual pointers.

ydotool is the generic equivalent. It works on both X11 and Wayland environments.

Autokey does not work yet, but there is Hawck and Espanso that you could play around with. And there is ydotool if all you need is simulating basic input (as in ydotool mousemove -x -10 -y -10, ydotool type 'Hello world!' and so on).

Does ydotool do what you need? I haven't even tried Wayland in years. I'm sure someday I'll find the need.