Well, not sure how many FOSS non-profits can say this, but... KDE e.V. and the @kde community just helped fund life-changing cataract surgery for a Ritchie that DESPERATELY NEEDED IT
AAAAAAAAAA
the text is so sharp!!!!
Well, not sure how many FOSS non-profits can say this, but... KDE e.V. and the @kde community just helped fund life-changing cataract surgery for a Ritchie that DESPERATELY NEEDED IT
AAAAAAAAAA
the text is so sharp!!!!
I don't condone child me's actions but I'll tell you what *did* make useful progress with respect to my bullying problem
telling one of my classmates to fuck off and throwing my laptop in their general direction
don't think calling someone a coward is nearly as bad
seeing my friend get nailed for calling someone a coward makes me remember something
in all my years of being blind and gay, and being bullied for it in school (in some cases *by staff members*), not once has respectfully reporting it to the principal ever gotten me anywhere useful, if anything I've been punished for it.
questions nobody asks but me: Who did they hire to voice the "Front Left" and "Front Right" voice lines in my Plasma audio settings?
people who pronounce it any way other than "butter fs" are objectively wrong because I said so
Does anyone have any recommendations for how I could set up an open source alternative to Google Assistant (the old one, not Gemini?)
My phone runs LineageOS, and I have an enterprise server.
It would be useful to be able to verbally set alarms, reminders, etc. on my phone/desktop. I also have lights that I'd like to be able to verbally control, and I have no idea if Home Assistant supports them.
if there's a next cloud, where is the previous cloud?
Shortly after that interview, Nate pulled me aside. Paraphrasing, he told me the board went with another applicant. But he asked that, if the rest of the board discussed and agreed, if I'd be willing to work with them as a brand new role.
I said yes.
And now, they have a KDE accessibility engineer. That's who I am. I write the code that makes KDE software easier to use for people with disabilities.
I am a KDE developer. I am proud to be one.
I applied as a software engineer at KDE e.V. in April 2025. I got the interview, with Nate Graham and Aleix Pol.
It was the first interview I've ever had. IN MY LIFE.
And it wasn't great.
I didn't get that position. Someone else did.
(not done)
the 3D bouncy ball in #kde is certified ritchie accessible
GNOME-chan
just my opinion but like
it probably isn't a good idea for a desktop environment to name itself and its utilities after characters from a known-to-be-very-litigious company's intellectual property...
just saying...
you know who you are...
I've learned (and am still learning) a lot about KWin specifically, and although it's *just a little bit* more complex than any "compositor" I've written for a hacking video game... It's fun.
I find working on KWin specifically has helped me be better at architecting my game engine since you'd be surprised how much they have in common in terms of graphics programming.
I've been working on @kde accessibility for a year.
And I'm up for a few more, as I slowly but surely make it easier to see my own PC :)
Looking for an artist/graphic designer to design a new logo+wordmark for my custom in-development FOSS game engine, Inertia. Willing to pay. It just doesn't have any kind of logo yet, and kinda needs one.
civil engineers: "corrosion is horrible and bad and destroys things and is really really expensive"
software engineers: "rewrite EVERYTHING in rust"
the ancient greek lord diabetes, god of sugar
Contrast this to TalkBack on my phone.
If I put my finger on something on the screen, it gets spoken aloud. Be it text, a picture, a button, an input field, something that's disabled, it doesn't matter. If I put my finger on it, it gets read aloud.
A screen reader needs to be able to focus on these non-interactive elements, not just rely on an input field declaring "I'm labelled by this label." There are interface layouts that do not have input fields associated with them, you can't rely on that.
We need some reworks in the Wayland land, I think.
People ask me why I never use screen readers on Linux. It's because they can only read interactive UI elements that currently have keyboard focus. Those aren't the only things I want to be able to read. It is impossible for me to just have an image description, or a label, or an icon, read aloud when I hover it. I'd have to navigate through a bunch of input elements to get to it in the first place, or use some weird shortcut.
The problem? I can still *see* my screen, but struggle to *read* it.