Tobias Frisch

@wiki_me My point is that the funding is optional and you can track all of Purism’s efforts via their Gitlab instance.

I agree that you don’t have fine-tuned control on what they should focus on. But I’m also not convinced users need to have this control.

Obviously it’s more transparent when you donate to individual developers manually instead of going through a company. I don’t disagree with that.

But in my terms it’s still an improvement.

@wiki_me I would like to see this model work. Because free software definitely benefits from funding and it’s far more transparent like this than financing software efforts with hardware funds.

@possiblylinux127 I feel like image to text processing would require unnecessary resources in many cases and have potential wrong recognitions.

Wouldn’t it make more sense to have some sort of extension to Wayland that allows annotations containing the text for screen readers? So toolkits like GTK and Qt could simply annotate text of labels, buttons and other widgets, avoiding image to text processing.

@possiblylinux127 That would definitely be part of it, I assume. Does Wayland already track text rendering and its contents?

Because somehow text from any UI would need to be detected.

@Chewy7324 @GolfNovemberUniform I’d say as soon as screen readers work properly under Wayland, they could drop X11 builds. But they should definitely not do it before fixing that.

@nick I don’t know. I can understand both sides.

Users searching for solutions of their problems, stumbling upon a new functionality and test it out without doing what it does.

Developers specifying what it does and therefore expect people would know what they are doing.

Anyway a compromise got merged to make it more difficult for users to accidentally mess up. Which is probably good. But I don’t think you need to handhold users all the time…