@thestrangelet@lucasmz It isn't the opposite. Aral is twisting words to claim people are not supporting accessibility. Everyone involved wants it to be better, so why throw around words like ableist?
@thestrangelet@lucasmz It doesn't feel genuine when someone targets others who are supposedly on your side, calling them things like "ableist" for not having finished their work. It reminds me of having been called a racist by Lunduke for supporting DEI...
I am unfollowing @aral. No matter my disagreements with GNOME folks in the past, COSMIC and GNOME are going to end up with the same accessibility backend, @accesskit, developed by the amazing @matt. Thanks to funding gathered by @gnome from @sovtechfund, rapid advances are being made in Wayland-compatible accessibility features. Let's stop concern trolling each other and instead work on building a better free software world for everyone.
When are we going to take Rust parsing seriously? Firefox 117.0.1 (and also Chromium, which means all Electron apps) had to fix a libwebp buffer overflow that could lead to remote code execution, and now Firefox 118.0.1 (and also Chromium, which means all Electron Apps) has to fix a libvpx buffer overflow that could lead to remote code execution _just two weeks later_. These are just two C libraries used by ALL browsers and many programs, handling remote input in an unsafe way!
We will be moving Virgo laptop PCB design to this public, GPLv3 licensed project: https://github.com/system76/virgo/. This will be the most open, modern x86 motherboard design I know of.
@system76 Principal Engineer, @pop_os_official Maintainer, and @redox BDFL - https://soller.devProfile picture and banner: I am wearing a Pop!_OS shirt with multiple computers running Pop!_OS in the background to celebrate the 20.04 release.