Search
45 results for “TheEvilSkeleton”
-
Hey, I've been under distress lately due to personal circumstances that are outside my control. I can't find a permanent job that allows me to function, I'm not eligible for government benefits, my grant proposals got rejected, paid internships are quite difficult to find. Essentially, I have no stable monthly income that allows me to sustain myself.
Nowadays, I work mostly on accessibility throughout GNOME as a volunteer, improving the experience of people with disabilities. I helped make the majority of GNOME Calendar accessible with a keyboard and screen reader — still an ongoing effort with !564 and !598 —which is an effort no company ever contributed financially. These merge requests take thousands (literally) of hours to research, develop, and test, which would have been enough to sustain myself for a couple of years if I had been working under a salary.
I would really appreciate any kinds of donations, especially ones that happen periodically to bump my monthly income.
These donations will allow me to sustain myself while allowing me to continue working on accessibility throughout GNOME, potentially even 'crowdfunding' development without doing it on the behalf of the Foundation.
I accept donations through the following platforms:
- “TheEvilSkeleton” on Liberapay: https://liberapay.com/TheEvilSkeleton/donate (free and open-source platform)
- “TheEvilSkeleton” on Ko-fi: https://ko-fi.com/theevilskeleton
- “TheEvilSkeleton” on GitHub Sponsors: https://github.com/sponsors/TheEvilSkeletonBoosts welcome and appreciated.
#Accessibility #a11y #GNOME #GNOMECalendar #MutualAidRequest #MutualAid
-
@TheEvilSkeleton Hey 👋. So there's this problem with the #refine app.
I doesn't identify the cursor theme that I installed. On my previous OS (which was also Fedora), it was able to do it. I believe since I had it on my root directory, that could be a reason.
Could you please look into it ?
-
@TheEvilSkeleton Hey, are you planning some new features for #Refine ?
-
@TheEvilSkeleton @CodedOre And there's this Keyboard option on #gnometweaks, it would be nice if you consider it. Then again, I think it mainly caters to power users. So, not a necessity but nice to have.
-
@TheEvilSkeleton @CodedOre I've to say, if someone enters the #Fedora ecosystem for the first time then, this is the by far the best app to try. It's simple and easy to use. However, the same can also be said about #gnometweaks.
#Refine is almost a complete package. And there's just one thing I would love to get added.
Having a detailed menu rather than a simple popup or you could do a detailed popup. -
@TheEvilSkeleton And then there's #Elive that has "impermutable mode" as a boot mode. That's where all local changes will be lost after a reboot. A nice way to do quick, worry-free tests (Yes even "sudo rm -rf /" :😂 ) and have your system spared and clutter free.
It's for us lazy people who hate back-stepping and repairing.😇 -
@TheEvilSkeleton I mean, this is just a specialization of social media. have you considered checking hashtags like #AppIdea ? if not on Mastodon, definitely on Twitter which is an endless torrent of random musings by consumers
-
Thank you @TheEvilSkeleton for taking the time to make #Meld work with #GNOMEBuilder, so that any #Python + #GTK #GNOME contributor can now easily test and improve that venerable textfiles comparison tool without having to figure out how to build the app by themselves!
This should also make the GTK4 port here easier for anyone to test and contribute to, once it gets rebased: https://gitlab.gnome.org/GNOME/meld/-/merge_requests/105#note_1875728
-
Huge thanks to @maximiliano and @TheEvilSkeleton for reviewing & merging this very long-awaited UX improvement in GNOME Calendar's infinitely scrolling month view: the previous/next buttons (and corresponding keyboard shortcuts) now properly clamp to the beginning of months when switching months! :blobmiou:
See the "before" vs "after" demonstration videos in the merge request: https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/369
#GNOMECalendar #GNOME #UX #productivity #calendaring #planning #OpenSource #FLOSS
-
GNOME Live Coding | Calendar (EN) | 03/03/2026 | Georges Stavracas
https://www.youtube.com/live/Tj5X7YM2Gos?si=LTa-OChY5kkslFgl
#gnome #gnomecalendar #coding #GTK4 #gtk #opensource #libadwaita #linux #foss @gnome @gnome_br @TheEvilSkeleton
-
The (un)fortunate side-effect of me attending the @XOrgDevConf this week is that I found a new #GNOMEShell performance issue to report about scrolling workspaces with a touchpad, because I saw what 60fps feels like on @TheEvilSkeleton's AMD-powered laptop and now I cannot un-see this jank on Intel graphics: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7976
-
@parrot_33
C'est une version vieille de 4 ans et demi. On a réglé plus de 455 bugs depuis, et on continue. Il faut utiliser v50+.Par pitié, cessez d'utiliser Mint et ses versions patchées à l'arrache datant de Mathusalem, on les supplie d'arrêter de packager notre logiciel de cette façon nuisible et jusqu'à présent ils refusent ou feignent l'incompréhension.
Voir:
* https://mastodon.social/@nekohayo/115810821753959688
* https://gitlab.com/linuxmint/pins/mint/gnome-calendar/-/work_items/1
@TheEvilSkeleton @sebsauvage @Natouille -
@parrot_33
Point du tout… j'utilise l'application presque exclusivement au clavier quotidiennement, et ça marche, incluant passer d'un champ à l'autre au clavier avec Tab (ou même d'un événement à l'autre avec les touches directionnelles, dans la dernière version), tel que démontré dans la vidéo ci-jointe.#GNOMECalendar met énormément d'efforts pour rendre l'application accessible autant que possible, majoritairement grâce aux contributions de code de @TheEvilSkeleton
-
All of this brings me to GNOME Calendar and @linuxmint. For years, we've been dealing with users reporting issues about Linux Mint's package of GNOME Calendar to us, that were either never present or addressed releases ago.
Just a couple of examples:
- https://pouet.chapril.org/@parrot_33/116374864921983890
- https://vmst.io/@doctroid/116542487573304110
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/300
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1562
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1535
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1526
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/work_items/1429
- https://matrix.to/#/!koZzDOwNHEzEoeuNok:matrix.org/$174759788212004HiyFg:gnome.org?via=gnome.org&via=matrix.org&via=fedora.im
There were a couple of discussions regarding this in the past, in chat, but none of it ended up being productive. Eventually, we got fed up by it and I opened issue #1 on Mint's package of GNOME Calendar — the first issue ever in their package's repository — asking them to remove all links pointing to upstream GNOME Calendar and rebranding the app. This had no response for 6 months, all the while we were still getting bug reports about Mint's broken package. @nekohayo eventually got fed up (again!) and pinged the packager. The packager replied with something completely unrelated and asked which modifications we did not like, completely ignoring our actual request. So, I just told him bluntly that we don't have the time to look through the code just to pinpoint specific issues, so I'll just loosely say "everything", and the only way for us to be happy is if they could rebrand and we can move on.
Then, the packager responds with something unrelated once again, ignoring the essence of my comment, and follows with a whataboutism — "As i said, 46 and 48 are used by millions of people right now in Ubuntu LTS and Debian Stable. Are you going to request Debian and Ubuntu stop shipping GNOME apps?" — in other words, "what about Ubuntu LTS and Debian Stable?" — as a bonus, twisting my words and going from GNOME Calendar to "GNOME apps".
So, once again, I reminded that this is not what the issue is about.
As a side note: no, never would we go after Debian or Ubuntu over this. If the distribution in question is doing its job properly by simply not bothering the people writing the software that they package, then why should we go after them? They are not the ones misleading users into opening in the wrong place, so there is no reason for us to be upset about. In this case, Linux Mint is leeching off of Debian, and pushing their responsibility onto us.
The packager then explains what to do, and redirects us to Debian to take down the package, essentially roping Debian into Linux Mint's problem — all the while completely ignoring the premise of this post. Sure, both Linux Mint and Debian's packages share the same source; however, this is just a technical detail. The actual problem, one that regularly affects us, is that Linux Mint users report issues to us, whereas Debian users report them to Debian.
So, I remind him bluntly that this is not our responsibility as an upstream to fix his problems.
He then suggests to incorporate code upstream to check if the user is running an outdated version or not. In other words, either phoning home, somehow keeping track of releases every 6 months, or something unrealistic.
I lose my patience and hostily tell him that we upstreams don't care about how distributions operate, and reminded, once again, that all we want is for them to rebrand. To which he replied with "If you don't care, then neither do we." — confirming that Linux Mint doesn't care about Debian or even itself as a distribution. Then says "probably requires GNOME Calendar to move away from free licenses" and locks the issue — once again, completely ignoring the essence of this entire issue.
Now they know what the problem is, and have refused to act on it by shoving their responsibilities onto us, but this time intentionally, because that should show upstream for hurting my feelings, never mind the fact that we are the ones doing the hard work, and they are making us do more work. This is the length some distributors will go to abuse people's generosity.
#MaintainerLife #Linux #GNOME #GNOMECalendar #FOSS #OpenSource #FreeSoftware
-
The Linux desktop has a maintenance problem due to the lack of volunteer contributors. One reason for this is that upstream projects are at the mercy of downstream distributions, who have the final say.
As an upstream contributor, you have no choice but to meticulously plead for any reasonable request to be granted by downstreams, treating them as if they were some kind of deity. Not doing so with the utmost respect can get you on their naughty list, which they can then use against you just because they can, and because the license allows it — they will even play the 'you chose the wrong license' card when they have nothing else to say.
The idea that the distribution model expects users to report issues to downstream is no longer valid. In reality, many distributions advertise themselves as user-friendly. Users of these distributions are unaware of the distribution model, so they report issues to upstream rather than downstream. Often, these bug reports and feature requests have already been solved in previous releases, so the upstream has to regularly triage and close duplicate and outdated bug reports. This creates an additional burden for them because they end up spending their limited volunteer time managing these issues when it should be the responsibility of the downstream.
Whenever the upstream project reaches out to the downstream distribution and asks for a change, the response is usually with the downstream pretending to look for a solution by first asking for a list of bugs to be found and compiled, essentially shifting the responsibility back to upstream to start a virtual machine just to test the package and find bugs. If upstream objects to this absurd request, downstream proposes unrelated or unrealistic 'solutions', such as adapting the issue tracker or switching to a proprietary license, just to avoid doing any actual work. Eventually, when the tone of the upstream project changes, the downstream makes remarks on that tone and starts acting like they are the reasonable one; they end the discussion and continue misleading users into reporting to the upstream project, but this time intentionally and out of spite, just to continue avoiding taking responsibility and accountability.
#MaintainerLife #FOSS #OpenSource #FreeSoftware #Development #Linux
-
It's always a wonderful feeling when you get to remove 1,000 lines of code and fix a bug in the process: https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/702
-
Everyone, rejoice 🙌
Georges livestreamed himself reviewing and merging accessibility contributions in GNOME Calendar again, specifically the entirety of merge request !564, which introduces keyboard-navigable month cells. This means, as of GNOME 50, GNOME Calendar's month view will be fully navigable with a keyboard for the first time in its history! The only high-level goal that needs work now is conveying these information with assistive technologies properly.
Do note that the screen recording attached won't have any alt text, to avoid redundancy. Everything written below is a detailed explanation of the experience, and the recording is essentially a visual demonstration:
- When tabbing between events, focus moves chronologically. This means that focus continues to move down until there are no event widgets overlaying the current cell. Then, focus moves to the topmost event widget in the next cell or row. Tabbing backwards with Shift+Tab moves in the opposite direction.
- On the last event widget, pressing Tab moves the focus to the adjacent month cell. Conversely, pressing Ctrl+Tab on any event widget has the same effect.
- Pressing an activation button (such as Enter or Space) displays the popover for creating an event. Additionally, pressing and holding the Shift key while pressing the arrow keys selects every cell between the start and end positions until the Shift key is released, which displays the popover with the selected range.Both merge requests !564 and !598 took us almost an entire year to explore various approaches and finally settle on the best one for our use case. Everything was done voluntarily, relying solely on support from donors and those who share these posts, without any financial backing from other entities. In contrast, most, if not all, calendar apps backed by trillion-dollar companies still don't offer proper keyboard navigation across their views. In many cases, they haven't even reached feature parity. If it is not too much trouble, please consider funding my accessibility work on GNOME. Thank you! ♥️
#GNOMECalendar #GNOME #Accessibility #a11y #Calendar #GTK #libadwaita #OpenSource #FreeSoftware #FOSS #OSS #Linux
-
An update on GNOME Calendar: Georges livestreamed himself reviewing and merging parts of merge request !598, making the month view easier than ever to navigate with a keyboard!
This merge request introduces a coordinate-aware navigation system in the month view, which computes the coordinates of relevant event widgets and finds the nearest widget relative to the one in focus when using arrow keys. When tabbing, focus moves chronologically, meaning focus continues to move down until there are no event widgets overlaying that specific cell, which then moves focus to the topmost event widget found in the next cells or rows; tabbing backwards goes in the opposite direction.
To illustrate the sheer complexity of navigation in a calendaring app, here is Georges's live reaction:
"Wow, congratulations, this is looking INSANE, Hari... The hell is going on here"
— Georges, maintainer of GNOME Calendar - https://youtu.be/smofXzVwNwQ?t=1h24m6s
#GNOMECalendar #GNOME #GTK4 #libadwaita #accessibility #a11y #FOSS #OpenSource #Linux
-
Georges Stavracas is reviewing my long-awaited merge requests related to accessibility on GNOME Calendar in his stream 👀
https://www.youtube.com/watch?v=smofXzVwNwQ
https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/598
https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/564#accessibility #a11y #GNOME #Calendar #GNOMECalendar #libadwaita #GTK4
-
Irregular reminder that whenever Firefox does not work properly on a Google website, it's because Google intentionally makes the experience worse for Firefox
First screenshot is taken on Cromite, second on Firefox for Android
-
Taking the liberty to cross-post my involvement with Fedora Flatpaks; originally posted on Fedora Discourse.
4 years ago, I discovered Fedora Flatpaks, and developed a strong interest with the tech and approach behind it. After having a thorough understanding of it, I wrote two detailed articles about Fedora Flatpaks:
- https://fedoramagazine.org/an-introduction-to-fedora-flatpaks/ (2021/12/22)
- https://fedoramagazine.org/comparison-of-fedora-flatpaks-and-flathub-remotes/ (2022/02/09)
Mind you, I also designed the banners (just highlighting how much I cared about promoting it back then).
I also asked to open a Matrix room (2022/01/01), which was rejected:
https://discussion.fedoraproject.org/t/matrix-room-request-for-fedora-flatpaks/35622
As time went by, I started losing interest, because there wasn’t much progress with the project, and it was duplicating effort that could have otherwise heavily benefited Flathub and every party involved (GNOME, KDE, elementary, freedesktop.org, Endless Foundation, etc.), which would have benefited Fedora, too.
This realization led me to write “Where Fedora Linux Could Improve § Only Ship Unfiltered Flathub by Default”, which criticized the lack of progress with it, as well as addressing one of the “legal concerns” (2022/12/06):
(Side note: I’ve also heard from Flathub folks that they received legal advice in regards to these issues.)
This led to some community members to react and start the Flatpak SIG project, to accelerate development — 2 days after my blog post (2022/12/08):
https://fedoraproject.org/w/index.php?title=SIGs/Flatpak&oldid=662603
Then, a Matrix room was (finally) created and publicly available (2022/12/10):
https://fedoraproject.org/w/index.php?title=SIGs/Flatpak&diff=prev&oldid=663009
By the way, I was never reached out or invited to join the SIG, despite putting in so much effort and time to accelerate development.
However, despite that, I still tried to participate in the project, and added myself to the SIG as well:
https://fedoraproject.org/w/index.php?title=SIGs/Flatpak&diff=prev&oldid=663089
Any of my suggestions then were either rejected with no proper explanation, shrugged off, or sent to
/dev/null. And whenever I asked for source for obvious misinformation, it would be dismissed.I tried to push Fedora Flatpaks in a direction that would have been less controversial and more productive by limiting its scope, which would also enable us to allocate more resources on other stuff. However, once again, I wasn’t really taken seriously; at least I personally don’t feel like so.
Eventually, I lost every last bit of interest and removed myself from the SIG (2023/02/20):
https://fedoraproject.org/w/index.php?title=SIGs/Flatpak&diff=prev&oldid=669108
All this to say, I tried really hard to keep my opinions to myself, and communicate diplomatically with them; I even wrote articles after doing several hours of researches in the span of weeks to show my interest, but I was treated extremely unfairly in return. So this naturally led me to one conclusion which I still hold today: they’re not looking for diplomacy; they just want to do whatever they want, even if it ends up upsetting/hurting people and projects’ image — I have the same sentiment with RPM packagers, too.
-
Refine, an app to tweak advanced and experimental features in GNOME, has reached 100,000 downloads on Flathub!!
https://flathub.org/en/apps/page.tesk.Refine
If you appreciate Refine and have the means to help a developer out, please consider donating to support my work: https://tesk.page/#donate
#GNOME #GTK #GTK4 #Libadwaita #FOSS #OpenSource #Flathub #Flatpak #Refine
-
Upscaler just reached 200 thousand downloads 🥳
https://flathub.org/apps/io.gitlab.theevilskeleton.Upscaler
#Upscaler #Upscaling #GNOME #libadwaita #GTK #GTK4 #FOSS #OpenSource #OSS #FreeSoftware #Linux #GNU
-
After two weeks of writing, revising, and trying to make everything as digestible as possible, I finally published "GNOME Calendar: A New Era of Accessibility Achieved in 90 Days", where I explain in detail the steps we took to turn GNOME Calendar from an app that was literally unusable with a keyboard and screen reader to an app that is (finally) accessible to keyboard and screen reader users as of GNOME 49!
https://tesk.page/2025/07/25/gnome-calendar-a-new-era-of-accessibility-achieved-in-90-days/
#GNOMECalendar #GNOME #Accessibility #a11y #DisabilityPrideMonth #Linux #FOSS #OSS #OpenSource #FreeSoftware #GTK #libadwaita
-
Starting from version 3.1.2, the GNU Image Manipulation Program will have the option to respect the system color scheme on Linux, thanks to XDG Desktop Portal and @nielsdg's merge request that was used as a foundation. Every desktop that supports the Settings portal interface will be able to make use of that functionality.
-
Introducing Refine 0.5.0, the GNOME Tweaks alternative leveraging the data-driven and composition paradigms. This version re-adds the Document font option, and renames "Middle Click Paste" to "Middle Click to Paste Text" with an accompanying subtitle.
Thanks to @CodedOre, 0.5.0 also adds the capability to rearrange the titlebar's window buttons. This new feature also lets you add the minimize and maximize buttons.
While we thoroughly tested right-to-left (RTL) direction and keyboard navigation with a screen reader, it's worth noting that we're no experts. We welcome feedback from those who use Refine in RTL and/or with a keyboard and screen reader.
You can get Refine 0.5.0 right now on Flathub.
If you would like to help fund projects like Refine, please consider looking at the donation channels at https://dir.floss.fund/view/funding/@tesk.page.
-
Next version of Upscaler will have the option to scale images between 2x and 4x :)
https://gitlab.gnome.org/World/Upscaler/-/merge_requests/78
#GNOME #GTK4 #libadwaita #FOSS #Upscaler #Upscale #OpenSource #OSS #FreeSoftware
-
Upscaler now passes all the checks to be considered good quality app data :)
#Flathub #Flatpak #FOSS #FreeSoftware #OSS #OpenSource #Upscaler #GNOME #GTK4 #Libadwaita
-
I finally have the motivation to work on Upscaler again, for a bit :3
I spent a few days working on a pretty cool queue system. I think so far it works pretty well, but I'll need more time to refactor it, address some TODOs, etc.
So far the merge request is pretty large... (357 lines added; 80 lines removed): https://gitlab.gnome.org/World/Upscaler/-/merge_requests/68
I have no plans to support parallel upscaling. A single instance tends to take a lot of resources, so I prefer not to risk freezing people's computers.
Eventually I'd like to work on some sort of batch loading so that users don't have to open each image eventually, but so far I think it's heading in the right direction :)
#OpenSource #FOSS #Upscaler #Upscaling #Vulkan #GNOME #GTK #GTK4 #Libadwaita
-
Wow, Sourcegraph made their repository private, when it was previously source-available (code publicly available, but proprietary) and before that open-source.
https://eric-fritz.com/articles/sourcegraph-went-dark/
Once again, this is why Contributor's License Agreements (CLAs) are bad. They allow owners of the project to abuse the terms of the CLA. You are very much giving your rights to them.
Don't contribute to software with a CLA.
(Credit to @refi64 for letting me know)