Email or username:

Password:

Forgot your password?
TheEvilSkeleton's posts Back to profile
10 posts total
TheEvilSkeleton

GNOME 48 will include a new feature that allows users to limit battery charging. This will help preserve battery capacity on laptops and smartphones!

gitlab.gnome.org/GNOME/gnome-c

#GNOME

20 November at 15:16 | Open on social.treehouse.systems
Show previous comments
ck0

@TheEvilSkeleton I though this kind of feature was impossible on laptops at the exception of Thinkpads, because there is no OS access to the battery and charging controler access.

The only laptop maker which allows this and provides a Linux firmware is Lenovo with Thinkpads.

20 November at 21:28 | Open on tech.lgbt
Vagrant Cascadian

@TheEvilSkeleton

I presume this requires support in the hardware?

Or is this some clever workaround that requirement?

20 November at 21:38 | Open on floss.social
fossdd

@TheEvilSkeleton much thanks to @jelly for pushing this forward!

20 November at 22:55 | Open on chaos.social
TheEvilSkeleton

Rust may be memory safe, but it's certainly not sanity safe

25 October at 5:06 | Open on social.treehouse.systems
TheEvilSkeleton

Wow, Sourcegraph made their repository private, when it was previously source-available (code publicly available, but proprietary) and before that open-source.

eric-fritz.com/articles/source

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)

#OpenSource #FOSS #CLA #Sourcegraph

Wow, Sourcegraph made their repository private, when it was previously source-available (code publicly available, but proprietary) and before that open-source.

eric-fritz.com/articles/source

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.

20 August at 9:39 | Open on social.treehouse.systems
Drew DeVault

@TheEvilSkeleton @refi64 they once asked me to implement sourcehut support for them and send a patch and I was like... nah...

20 August at 10:13 | Open on fosstodon.org
TheEvilSkeleton
TheEvilSkeleton

GitLab will soon be able to follow your preferred color scheme! (automatic dark/light style switching)

gitlab.com/gitlab-org/gitlab/-

10 May at 9:54 | Open on social.treehouse.systems
TheEvilSkeleton

I'm sorry to inform you that the Year of the Linux Desktop isn't going to happen anytime soon.

@kde just closed the merge request adding the most important feature: shortcut for opening LinkedIn. Because of that, the LinkedIn portal proposals will not happen as well.

This is unacceptable and goes against all the definitions and implications of the free software philosophy and spirit. Without that feature, I cannot use Linux anymore. I'm going back to Windows, as they are the only ones who care about user freedom.

If you were skeptical of Kringe Desktop Environment's takes against free software, then here's legitimate proof of them not caring about end user freedom. I will never forgive them for what they've done. We were supposed to simp for Microsoft!

I'm sorry to inform you that the Year of the Linux Desktop isn't going to happen anytime soon.

@kde just closed the merge request adding the most important feature: shortcut for opening LinkedIn. Because of that, the LinkedIn portal proposals will not happen as well.

This is unacceptable and goes against all the definitions and implications of the free software philosophy and spirit. Without that feature, I cannot use Linux anymore. I'm going back to Windows, as they are the only ones who care about user freedom.

1 Nov 2023 at 15:51 | Open on social.treehouse.systems
Show previous comments
Sabella

@TheEvilSkeleton @kde how dare the world of FOSS not embrace, and then extend and extinguish.

1 Nov 2023 at 16:42 | Open on furs.social
aiM
@TheEvilSkeleton @kde doesn't XDG just support having links in a .desktop file that are automatically handled by your browser
1 Nov 2023 at 18:22 | Open on social.translunar.academy
Sotiris Parmakis
TheEvilSkeleton
James Scholes

@TheEvilSkeleton @matt Is this post supposed to contain a link? My client just shows some text that looks like a title of a thing, plus some hashtags.

27 Oct 2023 at 21:13 | Open on dragonscave.space
Drew Mochak
TheEvilSkeleton

Shout out to Kévin Commaille for improving #Fractal's performance by a *lot*

- gitlab.gnome.org/GNOME/fractal
- gitlab.gnome.org/GNOME/fractal

These commits aren't available in the stable version of Fractal, so you will have to get the nightly version as a Flatpak via GNOME Nightly: wiki.gnome.org/Apps/Nightly

Honestly, it doesn't even feel like a Matrix client anymore, in a good way

#GNOME

Shout out to Kévin Commaille for improving #Fractal's performance by a *lot*

- gitlab.gnome.org/GNOME/fractal
- gitlab.gnome.org/GNOME/fractal

These commits aren't available in the stable version of Fractal, so you will have to get the nightly version as a Flatpak via GNOME Nightly: wiki.gnome.org/Apps/Nightly

25 Oct 2023 at 21:12 | Open on social.treehouse.systems
Show previous comments
Amy 🇹🇭

@TheEvilSkeleton yoooo that's sick! I've been using Fluffychat rn and I can't wait to see how Fractal is gonna be like (I was very disappointed last time I've tried :P)

25 Oct 2023 at 21:29 | Open on sauropods.win
Ertain
jade

@TheEvilSkeleton Genuinely gonna switch when these hit stable ~~the gnome infection continues to spread~~

26 Oct 2023 at 4:55 | Open on ordinary.cafe
TheEvilSkeleton

You know, I'm really starting to empathize with the "toxic" FOSS developers/maintainers.

I took a break from @usebottles due to internal issues and eventually stopped contributing to it because everything we did always led us to a lose-lose situation.

I thought that focusing solely on Flatpak would solve most distro-related problems. Boy, was I so wrong. Distros continue to package Bottles with their inferior packaging systems (inferior in terms of desktop apps, except Nix, because it's one of the few good ones), even when we explicitly asked not to, for various personal and technical reasons. Users continue to ask for support on 6 month old versions of Bottles (no joke), and distro bros continue to package Bottles because """it's the spirit of FOSS""".

Now that @mirkobrombin is the only code maintainer again, he wants to switch from GTK4+libadwaita to Electron. Why? Because he's a developer with real feelings (shocker!) and wants to enjoy maintaining again. But noooo, now users are whining because OMG ELECTrON BLoAT!!!111

Cool, you don't like the direction? Fork the project. Oh, you don't have the time? Then why waste your time whining? Why are you trying to tell maintainers what to do with their free time? Seriously, you're not helping anyone.

It really sucks that many FOSS developers maintain great projects and get trashed on a regular basis. You as a user are not the main character of the universe.

To maintainers who regularly experience harassment and entitled users: I'm really sorry you have to go through this. You have my utmost respect, and I hope you continue to enjoy maintaining your software.

You know, I'm really starting to empathize with the "toxic" FOSS developers/maintainers.

I took a break from @usebottles due to internal issues and eventually stopped contributing to it because everything we did always led us to a lose-lose situation.

I thought that focusing solely on Flatpak would solve most distro-related problems. Boy, was I so wrong. Distros continue to package Bottles with their inferior packaging systems (inferior in terms of desktop apps, except Nix, because it's one of the...

7 Oct 2023 at 0:44 | Open on social.treehouse.systems
TheEvilSkeleton

The question is: Will Wayland, Flatpak, immutability, PipeWire, etc. save the Linux Desktop?

No, they won't, and they never will. What will save (or has saved) the Linux Desktop is a cultural shift in the community to make it robust, secure, inclusive, and accessible. Technical solutions cannot address social problems.

*This* is why we have systemd, Wayland, Flatpak, immutable distros, PipeWire and all these "next-gen" (some current-gen) technologies. It's a legitimate cultural shift to focus on making the Linux Desktop better for the vast majority of users.

You know what else would improve the Linux desktop? Getting rid of toxic users. Adding a code of conduct also drives away a lot of bigots, which is great for people who belong to marginalized groups.

Speaking of reducing toxicity, I realized that my original post caused one toxic user to switch from GNOME to KDE. And that's wonderful news for GNOME! This person has been making fun of GNOME developers (mind you, volunteers) for a while, and then claimed to be a designer. I hope they don't turn KDE into a hellhole.

The question is: Will Wayland, Flatpak, immutability, PipeWire, etc. save the Linux Desktop?

No, they won't, and they never will. What will save (or has saved) the Linux Desktop is a cultural shift in the community to make it robust, secure, inclusive, and accessible. Technical solutions cannot address social problems.

8 Oct 2023 at 13:26 | Open on social.treehouse.systems
TheEvilSkeleton

One thing I never expected about software development is how different contributing to an external free and open-source (FOSS) project is from maintaining a FOSS project. I thought they were similar, but they're not.

I get exhausted very quickly from constantly reading and reviewing code, as there are still many things I don't know about programming. Having to learn while I'm reviewing hits like a truck at 69420 KM/h. It also doesn't help that I feel pressured not to keep contributors waiting (not in the sense that contributors pressure me) when I'm busy IRL or want to work on something else.

Contributing code, on the other hand, is often as simple as sending a small patch, having it reviewed, addressing some issues and sometimes asking a few questions on how to address them, and you're done. Of course, it depends on what you contribute, as large patches can take a long time to be merged, but I enjoy contributing to external projects more than maintaining them.

Really, maintaining a FOSS project is time consuming and feels like a job - a job that doesn't pay you. I genuinely appreciate developers who continuously maintain code without getting paid the amount they deserve.

One thing I never expected about software development is how different contributing to an external free and open-source (FOSS) project is from maintaining a FOSS project. I thought they were similar, but they're not.

I get exhausted very quickly from constantly reading and reviewing code, as there are still many things I don't know about programming. Having to learn while I'm reviewing hits like a truck at 69420 KM/h. It also doesn't help that I feel pressured not to keep contributors waiting (not...

14 Jun 2023 at 14:31 | Open on social.treehouse.systems
Show previous comments
crzwdjk ✅

@TheEvilSkeleton I am lucky that I get paid to maintain an open source project, because it is definitely a lot of work, a large fraction of which is not actually coding. Doesn't help when the project was basically without a maintainer for a couple years.

14 Jun 2023 at 16:20 | Open on mastodon.social
Doomsdayrs :fedora: :matrix:

@TheEvilSkeleton everyday I go home, pull up shosetsu, and re-read issues

:ac_sad:

14 Jun 2023 at 16:57 | Open on fosstodon.org
TheEvilSkeleton

Honestly, most FOSS maintainers are in a lose-lose situation no matter their position, especially when they have a large userbase.

--

If they're too nice, then they're not going to express their controversial opinions on some matters to avoid conflict.

If they're "mean", then users will start harassing them, speak ill of them, etc.

--

If they're doing the work for free, then they're not receiving any money from it. If they need money and start "begging" for it, then users will hate it and might want to switch to something else.

If they're employed by a company, then they're going to be trashed for getting paid and not having the "true spirit of FOSS" and whatever project they'll be maintaining will be considered as "corporate infested" or any kind of synonym automatically.

--

If they have no way of getting data properly (e.g. telemetry, used features, etc.), including from less technically inclined users, then they won't be able to improve their software properly.

If they adopt some sort of telemetry, then users will call it "spyware" and might want to switch to something else. If it's opt-in, then most users will have it disabled anyway.

--

If they stick with more ethical platforms (GitLab, Matrix, etc.), then they'll lose many potential contributors, as they have a much smaller userbase than proprietary platforms. On top of that, they'll be worsening accessibility as the more ethical platforms often have worse accessibility.

If they use proprietary platforms (GitHub, Discord, etc.), then, well, it'll probably leave with some level of discomfort for relying on proprietary platforms.

--

If they continue to work on their project for a long time (especially for free) and start losing motivation, then they might still continue to maintain it to not lose the massive community they've built, but potentially be burned out by it.

If they deprecate the project, then users will think that the maintainers never cared for the community, nor did they care about their project.

--

(Just to be clear, when I say "users", I don't mean everyone. It's not meant to generalize.)

Honestly, most FOSS maintainers are in a lose-lose situation no matter their position, especially when they have a large userbase.

--

If they're too nice, then they're not going to express their controversial opinions on some matters to avoid conflict.

If they're "mean", then users will start harassing them, speak ill of them, etc.

18 Jun 2023 at 4:27 | Open on social.treehouse.systems
Go Up