This is great advice! It took me 2 years and many doctors before I wound up at a physical therapist who figured out my nerve issue in 10 minutes. It was wild how they could move my shoulder and reproduce it. Now I’m working on strengthening stuff to make it better—and keeping the setup for a defense in depth against other issues
I'm really tempted to get another one for use with my laptop, but I'm currently using a left-handed Elecom trackball that is wireless - it's fine, but not the sheer luxury of a Ploopy.
You may be interested in one of my current projects, I’ll post details when it’s done, but I stripped down a Crossland CC1 and am rebuilding it in an enclosure I can travel with.
Thanks for the correction, that was sloppy of me (usually I default to "they" when I don't know an author's gender). Too late to edit my comment now sadly.
Wayland kind of reminds me of the CORBA->DBus rewrite. GNOME 2 was awesomely accessible. Then came the "qwe need to switch to DBus" people, and basically destroyed the hard work of many years. For me, GNOME Accessibility never recovered from that blow. And then came Wayland, which made things even worse.
Tech's Gen Y seemed to have a big 'NIH' thing about things that predated them, and it seems to have continued with Gen Z. Resulting in a lot of things just being trashed for the sake of it 'not being modern enough'.
Various nerve stuff in my arms, limiting my use of keyboards. With an ergonomic keyboard I can get through most days, but I’m having more flare ups lately so I’m doing more voice coding.
I use Talon. It simply doesn’t support Wayland, and I believe its maintainer who says that there are issues with Wayland which make support infeasible. Using it on X makes my nerve pain much less.
- input emulation, doable via uinput but not great
- standard way to query the list of windows and active focus
- for dwell-click support, you need to be able to know if the user is moving their mouse or clicking so you can cancel your autoclick
The "update" is that the Teams Desktop Application for Linux was discontinued last year, and the only supported way to use Teams on Linux is now to open https://teams.microsoft.com in Google Chrome or Chromium (audio/video calls don't work on Firefox).
Since Chrome/Chromium supports screen sharing with Wayland, it simply just works for me nowy while it never worked with the Elecrton-based desktop application.
Screen sharing in Wayland is possible by capturing your window/desktop with OBS and streaming it to a virtual webcam that it can create for you. It's a minor hassle, but comes with the added benefit of filtering for your webcam. I use it to remove and replace my webcam background with a plugin, and it works for me in apps that don't have that as a feature.
My WM is i3. I know sway exists, but last time I tried it was sufficiently different from i3 to be annoying.
I think overall the problem with Wayland is that there is no user facing improvement over X that I know of.
I have no doubt it's more modern, better engineered, or whatelse. But in the end, the days of fiddling endlessly with your xorg.conf are over, and X _just works_ out of the box on any distro / device.
All Wayland bring me is a switch of WM, and some bugs when screensharing, for no visible benefit.
The only hope of value add I can see with Wayland would be per-monitor DPI. But last I checked, it was hackish at best.
If you can believe people on Reddit, multi monitor support on Nvidia GPUs is broken. I only run AMD so I don’t have that issue. A game mod I use for ET Legacy only runs under X.
I had a similar thing happen. I distributed some malware I wrote on the shared drive and had some people run it (it was extremely basic, just locked people out of the computer with no recovery by taking advantage of how locked down they were; but people lost a lot of work). My programming teacher, who was already dealing with me being a distraction in class, went to bat for me so I didn’t get strongly punished but made me clean it off the drive continuously; other students kept putting it back, so I had to monitor for it.