Have you filed a bug somewhere in the issue tracker? I don’t think anyone from the GNOME devs is using a surface, so if you don’t provide any info, there’s a good chance they don’t even know about it.

Note that Input Leap will be supported on a Wayland session in GNOME 45 / Fedora 39 thanks to the new InputCapture portal and Peter Hutterer’s libei work.

Barrier seems to be dead upstream and Synergy is closed source though, so those 2 probably won’t get updated soon

Note that there’s now a solution for this in Wayland compositors that support the InputCapture portal. This should work on the latest (or next? not sure) version of Input Leap and GNOME 45 (which launches as part of Fedora 39)

GNOME and KDE both support the desktop-agnostic xdg-desktop-portals which provide general desktop APIs and that’s what most DEs are now converging. The portals including screensharing, input emulation and much more. The problem is that sway/wlroots doesn’t want to support it as they’re somehow vehemently against a D-bus dependency

The new architecture allows developers to fix one thing without accidentally breaking 3 others.

That’s an extremely bold claim, and vague, with no actual examples.

The problem is not the code per se, but that we can’t add stuff anymore that doesn’t somehow break the core protocol. The plain fact is that we’ve been tacking on things to X11 which it was never designed to do for decades and we reached a breaking point a while ago.

Stuff like multi-DPI setups are impossible to implement in X11’s single-framebuffer model; security on X11 is non-existent, but we can’t retroactively fit any kind of permissions on the protocol as that breaks X11 applications that (rightfully) assumed they could get a pixmap from the root window. There’s so much more, just take look at https://www.youtube.com/watch?v=RIctzAQOe44

and support it properly, with stuff like reclocking now actually working

So there’s quite a few errors here:

• NVIDIA creating an open source driver (well, throwing code over the wall once in a while is still open source I guess) does not mean there’s an upstream driver. The kernel maintainers have already noted that it’s definitely not in any shape to be merged upstream (and would need close to a full rewrite)
• “He’s resigning because he thinks the community should focus on that driver instead now” is completely false and I have no idea how you even got to that conclusion. Literally on the same day he posted this email, he also posted initial GSP support which specifically gives us a bright future in nouveau, as it means we can now do funky stuff like reclocking (and which will be further developed by some other people in his team at RH).

Well, the other thing Ben just posted before leaving is the initial support for GSP in nouveau (now continued by someone else in his team), which means we can finally start doing things like reclocking. With this and other cool stuff like nvk coming up, we finally have a way forward to have a good upstream experience.

Both. Ben’s taking off for personal reasons (it’s literally written in his email, but people will still try to pretend it’s related to the recent kerfuffles with Red Hat)