not a single one of those compositors implement the entire API surface you need.

Aegis has requested that those of us who wish to not see Talon on Linux die out do the following:

• Do not, for any reason, discuss Wayland support with him;
• As a community, gather together, and successfully implement the entire API surface needed for Talon on GNOME, KDE, and wlroots,

At which point a new Wayland backend will be considered for Talon.

I agree that it’s not up to Talon to implement the missing APIs in the compositors. However, I think the dev is doing a disservice to the users of Talon by not adding wayland support (ie making the calls to the APIs Talon needs to function). If Talon used those wayland protocols, users could point to the software and say it’s “not working on compositor because the compositor is missing wayland protocols”.

IMO its a much easier sell to the compositor people when they know a useful piece of software is actively trying to target those APIs.

That being said, I sure hope the situation improves. The state of accessibility on wayland is pitiful.