Aren't AppImages still limited to Xorg?

Also there's no centralised update mechanism or dependency deduplication, no?

Jia Tan liked your comment

Without the traditional distribution workflow [...]

You are aware that the xz exploit made it into Debian Testing and Fedora 40 despite the traditional distribution workflows? Distro maintainers are not a silver bullet when it comes to security. They have to watch hundreds to thousands of packages so having them do security checks for each package is simply not feasible.

I wonder if that means it could be combined with DXVK to enable support on older DirectX versions as well. ^^

As someone who owns a PinePhone I can tell you that a lot more work needs to be done first. postmarketOS is ok but being Alpine based means you have to forever deal with all the issues that come with it including its primitive package manager. And mobian also kept breaking ever other half a year or so requiring manual config changes etc.

What we need IMO, is a more reliable spin like Fedora, maybe even something immutable like Silverblue to ensure the stability required for a daily driver device while also being quick to deploy the latest versions of releases.

There's also the whole app ecosystem aspect but between advances in Waydroid and convergent GTK apps, I'm more concerned about the underlying base OS than the app ecosystem ^^

I wish something like .config would be a thing for storing configuration files in repositories. Instead we have a .vscode, .github, .gitlab, .idea, .vs, etc

Not to be that person but I'm curious what made you go with AppImage over Flatpak, given that you already mentioned using the Flatpak as an alternative ^^"

The easiest way to block an auto-upgrade to Win11 is to just disable TPM in the BIOS. That way Windows will see the PC as not Win11 compatible and not perform the upgrade.

Looks interesting, I'll check it out, thanks :D

YAML would such a nice language for config files but then it turns out that "no" is falsy and so a list of Scandinavian countries turns from

• se
• fi
• no

into

• "se"
• "fi"
• False

I wish there was like a JSON5 equivalent for YAML that just reduces its scope lol
(and no, TOML also looks ugly :P)

They already use GitHub for a bunch of other projects. See https://github.com/mozilla/ and https://github.com/mozilla-mobile/

We should probably update this post given that vanilla is now playable ^^

The linked message is from 2019, i.e. per-M1 Apple laptops and at a time when arm in datacenter was just starting out.

Tbh, I feel like it's kinda pointless to discuss a comment made by someone over 4-years ago. Both the environment and the person itself can change a lot in that time.

I feel that at the very least, the customer in that case should be entitled to a complete refund of the product, regardless of whether they bought it 5 days or 5 years ago and regardless of the condition their device is in.

This should at least give some incentive to companies to not perform such sweeping changes to their terms of service and if they do, the customer can more easily remove themselves from the lock-in without taking a financial hit.

Or just use long-forms like

tar --create --file pics.tar ./pics

instead of

tar -cf pics.tar ./pics

or

tar --extract --file pics.tar```
instead of

tar -xf pics.tar

which is honestly way easier to remember... \^\^

It's currently one of the highest selling games on Steam and something tells me that previous server issues might also finally be resolved :>

Okay

So basically it’s just another GNOME release gotcha.

AFAIK, the extension developer needs to explicitly set each version of Gnome they support. Even when the Gnome version doesn't have any breaking changes, the extension developer still needs to update their extension to enable their extension for the new Gnome version.

On that note, screen sharing worked just fine for me on Wayland Fedora 38 with Zoom Flatpak.

Like seriously, I help maintain a mod for a game and 90% of our Linux issues come from Arch users x_x

Convenience for end-users and avoiding link rot is probably one of the reasons.