I woke up to a comment so smug, so perfectly soaked in gatekeeping and faux-righteous posturing, it earned its own blog post.
You want freedom? You want GNU/Linux to mean something?
Then maybe start by not telling disabled users to go fuck themselves with a smile.
This commenter thought they were defending "software freedom." What they were really doing was kicking people out of the room. Dismissing accessibility. Mocking effort. Pretending that cruelty is some kind of rite of passage. They quoted Stallman like it was scripture, ignored real-world experience like it was noise, and wrapped it all in condescension dressed as virtue.
I’ve spent over a decade in this ecosystem. Writing patches. Rebuilding broken stacks. Helping blind users boot systems upstream doesn’t even test. I didn’t "just install Arch and whine about the terminal." I lived in it. I survived it. I held it together when maintainers disappeared and no one else gave a damn.
But apparently, because I didn’t call it GNU/Linux™ and because I dared to talk about how this OS chews people up and spits them out, I’m lazy. I’m weak. I should "get a dog."
So I wrote a response. Line by line. No mercy. No euphemisms.
This isn’t just about one comment. This is about every time someone’s been told they don’t belong because they couldn’t learn fast enough, code well enough, or survive long enough. It’s about everyone who was pushed out while the gatekeepers patted themselves on the back for "preserving the spirit of free software."
You want a free system? Start by making it livable. Because freedom that demands you crawl bleeding through a broken bootloader isn’t freedom. It’s abandonment dressed in ideology.
And if this kind of gatekeeping is your idea of community?
You can keep it.
fireborn.mataroa.blog/blog/you…
#Linux #GNU #FOSS #Accessibility #BlindTech #FreeSoftware #Gatekeeping #DisabilityInTech #OpenSource #Orca #ScreenReaders #ArchLinux #BurnItDown #blogpost

reshared this

in reply to aaron

The thing that surprises me about the fact that you bothered to respond to this comment (I'd've probably done the same thing in your situation) is that it's made abundantly clear in several ways that the poster didn't understand (or maybe even bother to read?) any of what you wrote. At no point is the actual subject matter of your post addressed directly or indirectly, which is already bad enough, and then there's the mention of font rendering. I'm aware that's just a way to illustrate this user's supposed point and nothing more, but using this particular example in a response to your post is beyond low, especially when commenting from this GNU/Linux-powered high horse which implies a level of intelligence and general understanding of the universe far removed from those of us running Netflix vending machines.
This is one of the very few times in which I would have no problem justifying the removal of a negative comment. It brings nothing not because it's smug and full of destructive criticism, but because it's smug and full of destructive criticism toward... The wrong thing?
in reply to aaron

I hate that this is how you came across my feed, but also thank you for this.

I have been writing a "guide to Linux" for friends that have shown interest and I knew I needed to write something on accessibility and I'm glad to have another resource to pull from.

I also had been debating if I should warn about this kind of gatekeeping. And yeah, sounds like I need to.

in reply to aaron

This is one of the reasons why IC_Null exists. Why I stream at all even though I know many of the products and services I call out do not give a single f*ck.
While #accessibility anything-at-all has a huge preaching-to-the-choir problem inside and outside of companies, this is the other extreme. Accessibility issues are just challenges to overcome, and this is a bit of a hot take, is NOT entirely inaccurate; a lot of accessibility issues can be mittigated by user knowledge, and a lot of folks don't know how to best use the assistive tech they have access to. HOWEVER, there comes a point where the user is absolutely within their rights to decide a so-called challenge does not need to be as challenging as it is, see also: pick your battles.
To me, if a product meant to make me more productive instead slows me down because of a poorly coded UI, I don't see the point, freedom, GNU or not. Today, my choice is between an operating system that compromises my privacy and tosses upsells at me in every way it can, or a set of operating systems that, through "freedom fighters" like Gary No-like Users over here, I can never trust to stay accessible enough to get anything done from one day to the next. Welp ... phone home all you like computer, I need to eat.
in reply to Florian

And quite honestly I feel there's a lot of victims to this kind of mentality that aren't necessarily disabled end users, take @danirabbit and others who do a huge amount of work to make #linux #accessibility be better than the wonky house of cards it's been for decades. They've essentially inherited the user frustration, righteous anger and powerlessness that systematic neglect has created while ALSO having to defend the fact to actually include hoomans that aren't "the norm" when deciding if a button should be a button or a superFancyNewRustUICompositeWidgetLookHowCoolMyInheritanceSKillzAreTemplateFoundationUIClassAlsoFuckYouKeyboardUsersButton. Peeps who want a simple OS for, say, an old computer that's losing Windows access a shot, seriously go give @elementary a look and provide feedback, these folks actually WANT to fix stuff
This entry was edited (1 month ago)

aaron reshared this.

in reply to André Polykanine

@menelion We’ve put a lot of work into fixing any reported accessibility issues and at this point I think the daily experience should be fairly usable, but we could always use help identifying blockers!

We’re tracking known accessibility issues in this GitHub Project: github.com/orgs/elementary/pro…

@zersiax

in reply to Florian

@zersiax Thanks for the shout out 🙏🏼 I’m so glad that you can feel that we’re really trying to improve things. Between the gatekeepers and concern trolls it can be really frustrating to work in this space sometimes but every success story is hugely motivating. My experiences with folks like you and @fireborn have been extremely valuable and positive and I truly believe that putting effort into Accessibility is a rising tide that raises all boats
in reply to aaron

Just noting that with a FOSS project, every feature or task or documentation or even dealing with contribution, has to have somebody's remaining time on the planet exchanged to do the work, usually for free and without thanks.

That's not excusing people getting burned / publicly humiliated. But... how is what you are doing here to the annoying commenter, any different to what you are raging against when it was done to you?

in reply to degenerating degenerate

@hopeless Totally fair to ask, and I want to answer honestly.
That comment wasn’t from a burned-out maintainer or someone struggling to keep up. It felt like a drive-by dressed in faux-righteousness — mocking accessibility concerns, calling me lazy, saying I didn’t belong, and acting like using the word "Linux" instead of "GNU/Linux" invalidated everything I said. That’s not critique. That’s gatekeeping.
What I’m doing — in my first post and the whole series — is calling out systemic failure. Not because people aren’t doing enough, but because the default state of this ecosystem still excludes people like me unless we patch it ourselves. And I have. I’ve given time, written code, fixed bugs no one else would. I know what volunteer labor costs and respect everyone who gives up their time.
I also give thanks where it’s due. I have a whole post dedicated to it. I want to highlight the folks pushing things forward — and I will again in a future post that’s already in the works.
But I felt like that commenter wasn’t coming from burnout or good faith. They were punching down. They weren’t overwhelmed. They were dismissive and condescending to disabled users. That’s the difference.
I’ll always show compassion to people trying their best in a hard ecosystem.
in reply to aaron

I'm putting this question as honestly as I can. You are, as always on SM, free to ignore it or to answer it in any way you like. You say: "What I’m doing — in my first post and the whole series — is calling out systemic failure. Not because people aren’t doing enough, but because the default state of this ecosystem still excludes people like me unless we patch it ourselves. And I have. I’ve given time, written code, fixed bugs no one else would.". My question is: why do you bother? Obviously, the point of Linux on the desktop is not to get things done, it is, for a significant number of people, something else, whether the nebulously defined "freedom", to prove how wonderful the user is, or some other goal. Just as obviously, it's been more than thirty years, accessibility on Linux is going nowhere. Why bother with it? I would value your answer, whatever it is, only because I want to know, I am not saying you should stop bothering, I'm just asking why you do. Oh, and another thing. If this is in one of your posts, feel free to direct me to that, I haven't read all of them just because it's too depressing to be told of a disaster which doesn't need to happen.
This entry was edited (1 month ago)
in reply to degenerating degenerate

How is fighting back different from picking a fight?

I think the blog post, and the author in general, is pretty cognizant of the fact free software takes labor to produce. The author has also given credit where credit was due in previous installments; very explicitly not merely criticizing the Linux-centric ecosystem. However, if the culture of free software replaces exploitation by data collection and malicious advertising with exploitation by demands of charity and burned out volunteers, maybe it's not as much of an improvement as it is touted to be after all.

in reply to asie

@asie
Your reply seems completely unrelated to what I posted... my point is that the OP cannot say how awful it is be treated as he described, while attacking his correspondent in exactly the same way.

They should pick a position, either it is to be denounced to act like that towards others; or, the OP is right to act like that towards his "contributor".

If it's OK to burn people, no point to the post. If not OK to burn people, OP shouldn't burn this guy.

@asie
in reply to degenerating degenerate

No, I'd say my reply is related, specifically the first sentence.

To put it in more direct terms, my view is that what OP is doing is equal to "self-defense", which in practice often involves performing acts of offense! However, we as society tend towards understanding them as defensive in context; in this case, the context being that the author of the article was attacked by a commenter and thus expects the right to be able to respond in the same manner, using the same rhetorical tools. The tone has been set, after all.

Of course, this doesn't change the fact that this is a terrible way to be treated, because it is. However, whether it's justifiable in one case or another is a matter of personal opinion, and I think OP's response to the comment is at least somewhat justifiable in context.

Also, I question the premise of there being "no point to the post" if it's "OK to burn people", given the author's entire blog is essentially airing out personal grievances with the state of accessibility in the Linux ecosystem. If the author gets something out of it, even a sense of catharsis, that's clearly a point in and out of itself. Personal blogs are not products and they should, ideally, not become products.

in reply to asie

@asie If OP really believed that burning others for his catharsis is normal and okay, then he is not in a position to write a rage-article blaming others for helping themselves to some catharsis at his expense.

Having been mainly on the getting burned side of this (including on LKML) I think if we can recognize it is bad, we should try to not increase the amount of it in the world. Conversely if we understand kindness is good, we can strive to increase the amount of that.

@asie
in reply to degenerating degenerate

@hopeless @asie Where are you even coming from with this. I replied to you yesterday, thinking you were coming at this discussion in good faith. In summery, I feel that pointing out systemic issues and process flaws allowing accessibility to be sidelined is very different from going on a post about genuine struggles a user has with Linux, GNU/Linux, GNU+Linux, LiGNUx, whatever you want to call it (even though the same issues exist when running no GNU software) and saying you’re calling it the wrong thing, also you’re just stupid if you can’t make it work. At no point have I called a maintainer stupid. I have called a corporation neglegent, I have critisized design choices and project priorities, especially where the project creators clame the project is inclusive
in reply to aaron

oh this is gonna be such a good one.

I wanna do a similar thing. I haven't had the pleasure of meeting a troll like the one you are replying to in such a long time. Last time was with an admin of a Linux Discord server called Linux For All that insisted that I am wrong about a codebase I work on and that runs some of my code (Mesa). I find them frustrating but also refreshing. It's just the stupid trolls, instead of the regular shit I deal with, like upstream maintainers, now.

I'm a bit sad that the software stack I usually touch on Linux, the graphics stack, isn't really, well, at all useful to blind folks. Best it can be useful for is GPGPU to run an img2txt model on images, and if that is all, I could strip it down so much it'd be much more reliable.

Also, I am working on an OS. I am trying to make accessibility a native feature, not an afterthought - the OS is data driven, and I am trying to make it so that everyone can use it the same, whatever input and output is available to them. All GUI programs able to natively hook up to a Braille display or a TTS engine instead that runs as a core system service. Because the GUI is not built by apps for GUI first, with accessibility tools having to hook into the GUI, but rather the GUI is placed at the same level as TTS engines and other stuff - as a user-interaction shell. That facilities user - computer communication.

Because as it turns out making it more accessible tends to also make it less painful to use for me too even if I am not blind etc. To be fair, I don't know if what I am making is gonna be accessible to blind people. I am trying to build something I would be able to use while having those disabilities, though. I want to actually test daily driving it like that (no screen) for some months. To make sure I am not just being delusional.

Because reading a lot of the accessibility stuff makes me feel like I should only work in accessibility tech if I am disabled in the ways the accessibility tech is meant to help with. And maybe that is true - maybe I should stop caring about whether disabled users would be able to use my OS. But I don't want to. One of my closest folks is blind. She won't use the OS, since it's not Unix, but... Yea...

And not like disabilities is something someone chooses or is determined at birth. I might get the exact same disability in an accident. No clue what life might bring. And I want my computers be ready in case that happens. Maybe I should focus on that instead of "virtue signaling".

aaron reshared this.

in reply to ity [unit X-69] - VIOLENT FUCK

@ity This means a lot — really. There’s a particular kind of mental exhaustion that builds up when you’ve been running into systemic issues for years, only to be told by some smug rando that it’s your fault for not liking it enough. So when someone shows up actually trying to make things better, it cuts through all the noise.
What you’re building sounds genuinely exciting — not because it’s perfect (what is?), but because you're thinking about accessibility from the inside-out, as infrastructure, not a bolt-on. That mindset shift is everything. And even the fact that you're considering daily-driving your OS without a screen just to test it? That tells me more about your intentions than a thousand spec sheets.
And no — you absolutely don’t have to be disabled to work in accessibility. The fact that you care enough to ask questions, to test assumptions, to admit you might not know everything — that’s what matters. Not being blind. Not ticking a checkbox. Showing up with curiosity and humility. That’s what makes the work real.
You're not virtue signaling. You're listening. And that's rare as hell.
If you ever want to bounce ideas around or talk through weird edge cases, I’d love to. The ecosystem needs more people like you — not because you’re doing accessibility work, but because you’re treating disabled users as real users, not afterthoughts or charity cases.
Keep going.
in reply to aaron

I'd love to share more and bounce ideas! The core idea of the OS is that apps should transform data, which should be visualized by a shell. The shell, then, can display GUI buttons, or be hooked up to a TTS engine, braille display, etc. It's like, every app describes an API for how to interact with it, which the shell turns into a user interface. It's kinda like a more generic form of UI layout description languages, but instead of specifying layout of GUI things, they specify data. Stuff like, actions the user can take. Data that can be queried. What kind of data it is - some text, a color, a time & date, an image that might have to be ran thru an img2txt... If it can be interacted with. Etc.

So for example a chat app will say that there is a selector list, named "rooms/chats". It will say that there is a settings interface, naming all the categories and types that individual settings are, including descriptions. It will then say that there is also, depending on the selected chat, a list of messages, which consist of a user (custom queriable type) sending them, and their contents, and are ordered in some way. The GUI shell then takes this and builds a button GUI - settings icon, selector for chats, makes the user info viewable, etc. And there can also be a CLI shell, that allows making commands that would normally be button clicks, just a question of querying the app interface and directly interacting with it. And the result could be directly hooked up to a TTS engine. Those are just some ideas - the entire thing is meant to be modular, and the individual components are meant to be replaceable depending on the needs of the user, from a library of hopefully (unsure if I will be alone at it...) tested components.

This means that the OS should work more or less the same on a desktop computer, a phone, a computer without a screen and just a keyboard and TTS, a Braille display, or just about anything that you can write a shell for.

It's called a shell based on the idea of a "desktop shell" being the user interface a user interacts with.

At the core of the OS is a data flow engine, and that is also the case between drivers. Everything uses this unified data-driven format. The computer talks with itself and with the user in the exact same way, which means that its own communication is easier to debug and reason about.

I am highly optimizing this inter process communication - the thing should be able to run on a dual core 1GHz CPU with 256MB of RAM, after all.

in reply to aaron

I think part of the problem here, though I may certainly be wrong, is that people like your commenter are using their computer as some sort of emotional support to improve their own self-image or, more accurately, to understand themselves as being superior to everyone else. Leaving aside the amazing meaningless of such proof, (some people prove their superiority through self-sacrifice, some prove their superiority through improving the world, some prove their superiority through overcoming circumstances, and some prove that superiority by... reading man pages and writing patches when some program breaks...), Anyhow, leaving all that aside, I have no interest in proving my superiority by the operating system I use. A computer is a tool. That's all. So is an operating system. If it doesn't work, I go somewhere else. My difficulty over the past few years has been that the tools are becoming more annoying to use, Windows and Mac for reasons obvious to everyone,and Linux both because of people like your commenter and because of accessibility issues. I am not emotionally involved with my OS. My OS is not part of my identity. Apparently, for your commenter, it is? Again, I'm leaving aside the poverty of basing one's identity on that, it makes people who base their identity on entertainers look reasonable. Having said that, I really think this is a lost cause, like most accessibility through persuasion. It will be implemented through the law or not at all, like, in fact, most other accessibility for small groups. Given the way Linux development is structured, I don't think the law of any particular country has very much to say.
in reply to aaron

Ok, now I see a whole bunch of comments instead of just one. I found the article by following the breadcrumb "fireborn" from your follow-up post that took me to your post roster. I wonder if your site-generator shows a frozen version of the page when accessed from there?

This is the URL I landed on, which is different to the one you just posted, seems linked to a particular post ("-post-4-" as opposed to "-post-1-")so it may just be the way I accessed it or something. It's a bit weird, but no biggie.

in reply to aaron

>" I didn’t "just install Arch and whine about the terminal."

Years ago I tried a fork of a popular distro. I had a few things to fix, so I decided to compile it into a list and then post it to the help forums for that distro.I was accused of trolling, astroturfing, trying to make their distro look bad. They only got angrier when I tried to explain I found it easier to make a list and that I LIKED the distro. A lot of people in that community are socially maladjusted.

in reply to aaron

My first born is dyslexic. They have learned to compensate extremely well in terms of reading.

Shortly after their diagnosis I tried to get screen readers to work under Linux, debian based with the XFCE desktop.

All I wanted to do was click on a web page and get the computer to read the text so that first born could listen to the content on the web page so that they wouldn't have to read it.

I failed to achieve this. Or perhaps it was Linux that failed me this time?

in reply to aaron

oh wow, what a not-nice person. :(

But great blog post!

Even though I'm not disabled (except with my autism) and even though I'm not even using Linux, I want to thank you for your years of hard work.

As someone who uses Windows, I definitely agree with you. Linux isn't built for people. I want to be able to use my computer without having to configure and set up every detail of my system. Some things - like the Desktop - have to "just work". Even though I don't have any Apple device, I like how their ecosystem works. It's easy. It's handy. It's "built for people".

I wish I could use Linux. Microsoft did have some bad decisions with Windows, but at the current time, it's easier for me to keep using Windows instead of having to deal with Linux.

I don't know how to end this reply, to be honest. I kinda just want to say thanks again. :floofHeart:

This entry was edited (1 month ago)
in reply to aaron

This is easily the #1 complaint I hear from people who've tried Linux and walked away. It's not the learning curve that drives them away. It's the attitudes they keep running into from insiders. From an outside perspective, the Linux community (or many of them, anyway) looks like a lot of smug jerks laughing at anyone who's not already savvy enough. Well, huge surprise, a lot of people don't like that.
in reply to aaron

i love the immediate "um actually it's "GNU/Linux" not "Linux", "Linux" isn't an operating system, GNU is" like to fuck it is? Sure, GNU + Linux alone can provide the bare minimum of what can be considered a "usable" operating system, You're not downloading and booting GNU_25.04_amd64.iso. Sure, the utilities provided by GNU are important, but the utilities themselves are important in the same way eggs are important in a meal. You can't just remove the eggs from many dishes, but most people won't notice if you swap the eggs from chickens on RMS' farm for the UUChickens, or the Berkeley Poultry Distribution or the Busycoup (as long as the rest of the system works fine with them). And even then, just because it's important doesn't mean it deserves to be in the name, because um actually what you're referring to as GNU/Linux is in fact, GNU/systemd/GNOME/Wayland/Pipewire/NetworkManager/OpenSSH/cURL/OpenSSL/Linux
in reply to aaron

Reminds me of what I call the “Bad Old Days” of Linux. It’s only since 2020 that I switched completely.

For the 10 or so years prior, every time I tried to install or use nearly any Linux distro and needed help, I was met with a hand to the face from the RTFM crowd. Forums were full of gatekeepers and basement-dwelling neckbeards who mocked anyone who didn’t already know how to manually create disk partitions and compile their own software.

in reply to aaron

I think that it's horrible that you got this reaction as a *nix user (BSD and Linux). Shitheads like that should be yeeted into the sun.

I don't like apple and Microsoft for a couple reasons (FOSS, monopolistic practices, Palestine/BDS compliance), but it doesn't matter if they're the only options that let you use your computer. And I'm not disparaging people who aren't as skilled with technology as me by any means because I'm not a jerk.

We really need more a11y on Linux for real.

in reply to aaron

I was cured of any interest in the Stallman viewpoint when I met him in person last century. Some excited nerds approached him to offer him something. They'd printed a Star Wars poster featuring the heroes of the story w heads replaced by Torvalds, Wall, Raymond, Stallman, etc.

Stallman refused to talk to them other than to complain that his head was on R2D2's body, like the droid was a useless character.

I forget the details, but I believe those guys grew up to become Windows ME.

in reply to aaron

Having now read the reply to the Reply-Guy, I'm honestly confused what they're on about. I just want them to do what they're supposed to. Having to dig into the system in order to fix something integral to its function?

Who's got time for this? Imagine a another system where you have to dig into internals when it fails to perform? Don't want to debug your microwave because the popcorn doesn't pop? Won't recompile the firmware that spins the turntable in the microwave? Lazy.

in reply to aaron

The whole accessibility and spying on you dichotomy compared to Linux is purely because these people have created that situation. Make Linux accessible and the false dichotomy disappears. In what alternate universe is accessibility predicated on user surveillance? No, it's ultimately because you're too lazy and lacking in broader understanding and empathy to get the bigger picture.

Idiots.

in reply to aaron

> You're not being excluded -- you're being challenged.

The idea that there is a hurdle someone should have to overcome, in any context, to be deemed worthy of freedom makes me sick to my stomach.

This user seems to acknowledge the fact that, at present, people with the ability to use Linux as a daily driver, with the ability to own their machine and do what they want with it without DRM etc etc., are few and far between, but rather than believing that everyone should have freedom and viewing that fact as a problem to be solved, they see it as a perk. Having jumped through all of the hoops to be able to use Linux, which most people justifiably refuse to and which some people physically cannot, makes them part of an elite club and gives them an excuse to feel smugly superior to Windows users, and that's the only part that matters to them.

People *should* be able to use free software with the same ease and same skill floor as proprietary software, actually. Foss bros can fuck all of the way off.

This entry was edited (1 month ago)