While celebrating my previous post of working call audio @pvagner@fedi.ml left this excellent comment:
https://ani.social/post/34656971/17805917
And this reminded me something that i and many devs sadly often forget, if its works for me it doesn't mean it works for everyone.
My philosophy is that linux should be as accesible as possible, nobody should be forced to be stuck with big tech.
So i tried my best to add orca screenreader support to plasma-mobile.
I mad this statement on my previous post
But a successful one!
But i genuinely don't know if i can claim that today, i don't use a screenreader so i don't know what the user experience should look like. I will glady incorporate feedback.
As with my kernel patches i will be working to upstream this with KDE, since this is probably not controversial i think it should be accepted quite quickly.
Small celebration:
I was quite happy when i saw this in my inbox:
https://lore.kernel.org/all/20260722234221.884765-8-srinivas.kandagatla@oss.qualcomm.com/
+maintainers:
- Jorijn van der Graaf jorijnvdgraaf@catcrafts.net
- Srinivas Kandagatla srinivas.kandagatla@oss.qualcomm.com
It looks like im being upgraded from linux contributor to linux maintainer!
Selling fp6 with pmos preflashed and with my patches preinstalled
Some comments mentioned this and it got me thinking, would there be demand for this?
I would be selling them on my catcrafts.net website, payment methods would be my bunq so wero, bancontact, credit card and crypto.
If you are interested in this, please upvote my comment, ive been looking into this and there is quite alot of administration that comes with it, so i would like to only do this if there is actual demand.
I would be shipping to any place i can. I will be shipping from the Netherlands, so keep that in mind for import duties and shipping costs.
On Android, SherpaTTS pulls in a number of different Piper and Coqui voice models. They definitely sound a lot better than this.
https://github.com/woheller69/ttsengine
The problem for screen reader users is that the better the voice sounds, the slower you have to use it at. And screen reader users generally like reading things at high rates of speed, and so generally are more willing to put up with the lower quality voices to get the faster speed.
For something like your map application that says in 300 feet turn left onto X name of road it's fine but for a screen reader user it's a problem.