I’ve had no issues with the ProtonVPN flatpak on Fedora Silverblue.

The Change proposal has been withdrawn by the author: https://discussion.fedoraproject.org/t/f43-change-proposal-x11libre-system-wide/156330/57

Updated the title

You can check if you are using Xorg or Wayland in the Settings -> System -> About -> System Details page. If you’re using Wayland, you’re all good, nothing changes. If you’re using Xorg, you may notice some changes. If you’re using NVIDIA on Ubuntu 24.04, you’ll be on Xorg by default. If you’re using a later version or AMD/Intel, you’ll be on Wayland be default.

To keep it short, X11 was the old protocol for creating and managing windows. Xorg implemented this protocol. But both the protocol and implementation have many shortcomings that are difficult to address for a multitude of reasons (breaking compatibility, poor code base, a ton of work, etc).

Rather than putting lipstick on a pig, a new protocol, called Wayland, was created. It was designed for modern needs and tries to avoid the pitfalls that X11, Windows, and MacOS have. It doesn’t just copy what those three did, it’s more opinionated, so some people love it a lot (like me) or hate it a lot because it changes the way things have to be done and simply does not implement some functionality, either purposefully or because the work hasn’t been done yet.

Getting ready for Zoom to have instructions to install i3 rather than fixing their Wayland support.

Keeping the search terms in the URL bar rather than replacing it with the URL is nice. Should help with searches on web engines that don’t support bangs.

I hope the https hiding doesn’t affect copying the URL.

The battery life is still better than most laptops, but yeah, not as good as MacOS.

It’s meant to be an upgrade over the old system. If both are accessible, that just means they didn’t remove the old code.

I use Silverblue and MacOS daily, I enjoy the former so much more.

Unfortunately my relatively new Lenovo laptop has a small but also major driver bug that hasn’t been fixed in all the time I’ve had it. Bad to the point I got the Mac to have actual working hardware. But I do not enjoy MacOS in the slightest. At best I can say it harasses you less than Windows and respects the user a few degrees more than Windows.

Don’t believe so, best that’s currently available is skimming through the video to look at the slides.

Here’s my short summary of the presentation, I tried to denote what’s being worked on (open PR), what’s kinda being done (WIP), and things stuff they’d like to be done in the future (wishlist). May be somewhat wrong.

• Flatpak is stagnant
• Red Hat is working on a better way to preinstall flatpak apps (open PR)
• Flatpak should is slowly moving towards OCI and away from ostree (more tooling available, don’t need to maintain their own tools)
• Better permission handling that is more backwards compatible (open PR)
• Should directly use Pipewire instead of Pulseaudio (WIP)
• Allow user namespaces in flatpak sandbox (WIP)
• Move dbus proxying into dbus brokers (wishlist)
• Improve network sandboxing (wishlist)
• Improve drivers handling, currently drivers need to be built for each runtime, could cause issues if using EOL app on new hardware (wishlist)
• Work on portals directly improves flatpak

Unfortunately, it’s not in a great situation. Flatpak is stagnant. There’s a lot of cool things in the works, like a stronger sandbox, preinstalling flatpaks more effectively, etc, but merging things is hard.

FOSS also depends on them, many FOSS contributors are employed by proprietary companies.

I love when I try to open a file and macOS tells me I can’t because can’t tell if it’s safe. There’s literally no way to open it from here.

You have to hit ok, then go so settings, scroll down to security, and hit a button to specify yes I actually want to open this file. It then reprompts you again but now with an open anyway button.

I love my MacBook’s hardware and battery life, but MacOS is such a letdown.

This is overly complicated. Just install Java then run

flatpak --user override --env="FLATPAK_ENABLE_SDK_EXT=openjdk" com.vscodium.codium

Note this works for all other SDKs too. It works especially well for programming languages like Rust that have their own package manager.

Doesn’t work so well for languages like C/C++ where you use your distro package manager to install dependencies. In those cases it’s easier to install VSCodium inside a container where you do have access to a distro package manager.

Fedora IoT is similar to CoreOS, that seems primarily aimed towards Pis.

@Zamundaaa@discuss.tchncs.de

I was wondering about that too. At first I assumed they were only allocated a few of the cores for their testing, but a typo seems more likely.

Mozilla is independent. All the search deal really is is that Mozilla sets a default option to point to Google’s URL and not another. In exchange, Mozilla gets millions of dollars.

The reality is that the majority of users would choose Google even if it wasn’t the default. So Mozilla is both providing the most popular option as the default and benefitting from it.

Anyone who doesn’t trust Google, such as me and presumably you, have the freedom to change the default.

Overall, I don’t think Mozilla is wrong. Without the Google Search deal, Firefox will have less resources to build a competent browser.

But Mozilla has also done a poor job at becoming financially stable without this search deal. It also doesn’t help that Mozilla’s CEO’s salary keeps going up in spite of the declining market share.

It would have been nice is Mozilla was able to fill a niche like Proton: building a suite of secure and private services. But instead they’re moving towards advertising.

I’ve never needed to downgrade Firefox.