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 ^^"

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/

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.

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... \^\^

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.

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

So far, Fedora has been rock solid for me ^^

yeah, tunneling into your local network and then calling WoL from there is the way to go.

ngl, I’m annoyed whenever someone creates an application but doesn’t want to publish their code cause it looks bad. Like no one cares that your code is bad and by publishing it, you can get others to help you improve it.

This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.

It’s like when an intern accidentally drops the production database. It’s not the interns fault for sending the wrong command. It’s the managements fault for not restricting access in the first place.

Not selfhosted but I think Pocket also falls into that category of service.

Also, you can just download an older version of the toolchain and use that to compile the project. If the project is properly setup it’ll tell you the toolchain version it used. If not you can probably guess by the time of the last commit ^^

It’s been a while since I last checked Vaultwarden (back then it was still called bitwarden-rs). If they added an export feature, then that definitely makes things easier. The export feature in the client isn’t enough IMO. Last time I tried it, it didn’t export attachments. So if you for example have your SSH key saved in Bitwarden, well then good luck if you loose access to the vault :P

While Vaultwarden is great I would not suggest selfhosting your password manager unless you do regular backups. Losing all your password cause your server went down is a great way to ruin your day.