The year is 2008. An application is doing something wrong with the accessibility APIs.
Orca decides to have a special case for it, to avoid bothering the app.
14 years later, that special case has been duplicated and refactored, so that all apps can afford being wrong in an extremely subtle way.
The original app is not fixed yet. Its relevant code has not been touched since 2003.
Trim video files as easily as it gets. https://flathub.org/apps/details/org.gnome.gitlab.YaLTeR.VideoTrimmer
Part of our work at Endless OS is around the usability of the GNOME desktop, guided by user testing. We're looking for test subjects for a 1-hour session, who are tech-savvy experts—e.g designers/developers, animators/…—with exposure to various devices & platforms. Bonus points if you're based near someone in the team—e.g. London—so we can put a laptop in front of you. Ping me here or to wjt@endlessos.org if you're interested!
I had to repost this from https://mobile.twitter.com/itsashtick/status/1547095485512564736#m because it’s adorable
> “ Probably a great many famous stories could be retold in terms of maintenance.”
Stewart Brand on the role of maintenance and planning on the solo-round-the-world sailing prize of the late 1960’s.
Have y’all heard Blender is moving to Gitea? Neat!
Community issue question
I've got a question for you fedi. There's a public issue tracker I regularly participate in. Since it's public, anyone can join as long as they follow the rules. However, there's a problem with someone who isn't breaking the rules but is causing (imo) issues.
There's a person who shows up on the issue, dropping walls of text and unimplementable mockups on every other issue. When this starts happening it basically kills other discussion in the issues. And they've been doing this sort of thing nearly every day for this past year.
They're not breaking any rules, but their method of engaging is very disruptive and IMO frustrating. There are issues I've wanted to follow the progress of, and then they've ended up filling them and making me unsubscribe. I imagine it's the same for others.
Has anyone dealt with this sort of thing before?
I am pleased to announce that #ThisWeekInGNOME is having its first anniversary! There has never been that many news as this week in the whole year!
#52 Happy Birthday!
https://thisweek.gnome.org/posts/2022/07/twig-52/
Microsoft has asked Lenovo to make it harder to boot Linux on their computers.
obviously I know some really cool people who work at Microsoft but it's very funny to me that people have been harping on us FOSS types for not instantly forgiving them for 20 years of malice, and now we've got this. [1]
when Microsoft is asking manufacturers to prevent people from booting other OSes and not communicating as to why, they are positioning themselves as the enemy. it's that simple. if they want to be trusted by Linux users, they need to earn that trust.
we're about 2y away, by my estimation, from living in a bizarro world where x86 PCs are less open to free desktops than ARM Macs.
""What was the previous electrician thinking?""
submitted by KiFrost
https://reddit.com/r/ProgrammerHumor/comments/vwbz0a/what_was_the_previous_electrician_thinking/
https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/class.AboutWindow.html
One more widget in Libadwaita. This time a GtkAboutDialog replacement.
Fixing test coverage reports in at-spi2-core - https://viruta.org/fixing-test-coverage.html
Arreglar los reportes de cobertura de pruebas en at-spi2-core - https://viruta.org/fixing-test-coverage-es.html
Rare work toot alert!
I wrote an article for Endless OS Foundation's blog about our approach for collaborating with #GNOME since becoming a non-profit, the work we did in late 2020 and 2021 on GNOME 40 and GNOME Software 41, and what's coming next.
(Dear reader, please be aware that by being on Mastodon you are almost certainly more technical and/or open-source-savvy than the primary target audience for the foundation's blog!)
https://www.endlessos.org/post/reimagining-the-open-source-pc-desktop