S
@mcc it's possible my perception was warped by the online player piano enthusiast communities I found, but my perception was that because these things take up so much space and cost so much to fix properly, it was a rich old person's hobby, like collecting classic cars
That said... sometimes there are ways to sort of fix them IMproperly, for a few years, so it's possible that is a more widespread practice than I thought?
@mcc I have difficulty believing the player piano numbers here... I bought an old busted player piano years ago, thinking, oh, it'll be fun to learn to fix this thing up! But it turns out "fixing up a player piano" basically means "reverse-engineering and rebuilding more than 88 individual custom hand-built wooden bellows" as table stakes, because the rubberized fabric starts leaking air after about 20 years, so even if it was perfectly restored in the 90s, it's fucked now.
@fireborn Like, the reason there is this enormous maximalist list of demands for what Wayland needs to provide to support Talon is because that is how Wayland structured itself. It is designed to place all the power in the compositor, and to prevent any other component in the system from co-opting that power unless there is consensus that there is a good reason and it can be done in a controlled manner. Under that framework there's no other possible outcome.
@fireborn yeah, I feel like the Wayland mindset is "these things are the compositor's responsibility, any exceptions need to go through a limited protocol and have their use cases thoroughly vetted to prevent abuse"
And the Talon mindset is "the user knows their accessibility needs better than me, so I will give them complete, straightforward programmatic control over everything"
The only way I can see of reconciling these two mindsets is for Talon to become a compositor
@fireborn Oh. Oh no.
I used Talon for a bit a few years ago when I was having shoulder problems. It's an incredible empowering technology, a fundamentally new and different way of interacting with your computing. It's also fundamentally built on the premise of scripted low-level control of the entire system UI. This is what makes it so empowering; there are no limits to how it can be extended.
Wayland is fundamentally designed to prevent such automated control. This is probably irreconcilable.
