I have seen mockups of GNOME adapting a similar banner style as what Flathub. We might have to wait for GNOME 47 though.
I have seen mockups of GNOME adapting a similar banner style as what Flathub. We might have to wait for GNOME 47 though.
Here I am chilling with Amberol
I vaguely remember some money calculating-related project guy who received a PR that heavily optimized and updated the project. Since he was very busy and no longer really wanted to maintain the project, rather than reviewing and merging the commit, he gave the contributor complete access to the repo for them to maintain the project at their own discretion. The project was unpopular back then—when he looked back a few years later, he was surprised to discover that the project had racked up several thousands of stars.
BlueBuild and deploy your customized image to the devices
Fourteen pages of comments within a day of posting in Phoronix? Grab your popcorn guys 🍿
IMO Flatpak is the best of them all. I don’t want to bother with repo packages that have complete and unnecessary access to my system. Flatpak neatly installs an app and isolates it, and if I no longer want it I can just easily click “Uninstall” on my Settings app without it leaving a mess or any trace behind, unlike repo packages that manage to screw something as simple as uninstalling itself.
All of the points of the previous comment are actually valid. Plus, immutable distros are much safer and easier to tinker with than traditional mutable distros. For example, an extremely specialized Arch setup would be much more stable and easier to jumpstart if it was a personalized Universal Blue image, even all your Flatpaks can be declared and installed at setup.
binex-dsk is now shadowbanned on GitHub
Evil Wayland is making their app crash
Sorry for the Windows emojis lol, I’m on a computer shop as I post this on lunch break
On much more recent driver versions Wayland support has been further improved. I suggest going with Fedora Silverblue since RPM Fusion is pretty quick to roll out new driver versions.
This is not nice.
You may have skipped some steps
deleted by creator
Well, no matter how I trust my photo editing app, it has no business accessing my thesis documents. Proper filesystem sandboxing does security properly.
The file picker API is there to allow apps to access and save files with the user’s consent, while bot having any filesystem access. So a properly sandboxed app would be able to open, edit, and save files wherever the user wants, while not having access to any other irrelevant files, such as your .bashrc or memes folder.
As I mentioned in my previous comment, they use the portals API to access and save files.
An app should not be able to access stuff the user did not consent to letting access.
As well as FOSS too. Sandboxing is a security standard that should be followed by every software how open their code may be.
As for the permission popups, they have already done that through XDG Desktop Portals. You might have noticed that, for example, apps with supposedly no filesystem access can still open files you selected via the file picker or opened via the file manager. Or that apps need you to explicitly allowlist them to access your location data. Those are apps that use the portals permission system. Unfortunately not all apps use portals yet.