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.

I just went on a journey looking at different local music players.

Just tried Rhythmbox. It’s not terrible, but not great either. It looks very bare bones.

Of the ones I’ve tried, I like Elisa the best. I spent a ton of time getting HQ artwork and quality metadata on my files and Elisa really shows that off. Rhythmbox barely shows any artwork. I just have two complaints about Elisa. First, Qt apps just don’t feel right in Gnome for various reasons: fonts are often too thick, icon contrast is bad, and Qt theme is weird for non-Breze. It also has weird scrolling behavior: it has forced scrolling smoothing and acceleration.

Runner up is Sayonara. It’s Qt based, but actually feels decent in Gnome. Overall I like the UI more than Elisa, but unfortunately it doesn’t handle showing my library as well. Artwork is duplicated (it shows albums multiple times if songs in them have different years) and some artwork is inexplicably missing.

Yes. Ubuntu has two main repos, main and universe.

main is relatively small and includes everything that comes with Ubuntu by default. Canonical secures this repo with security fixes for everyone.

universe is not officially supported by Canonical. It’s updates are done by community members. However, Ubuntu started a service called Ubuntu Pro / ESM that provides updates for packages in universe. It’s opt in because Canonical wants companies using Ubuntu to pay for Pro in order to help fund Ubuntu. However, Pro is also free for personal use on up to 5 machines, so there’s no reason not to enable it. f it was enabled by default then no one would pay for it.

I’m sure some laws would considering you making this post or me writing this comment as “selling” data.

Are you sure about that? KDE has a feature that lets Xwayland apps snoop if certain keys are pressed, but Gnome does not.

The traditional insecure global shortcuts system works in Xorg.

Make sure VA-API is enabled in about:config with “media.ffmpeg.vaapi.enabled”=true. It should be enabled by default in nightly.

Fedora Flatpak exists to match Fedora’s philosophy on FOSS, patented software, and security.

Everything in Fedora must be FOSS and free of legal issues, like codecs. Fedora also takes security seriously, so all their Flatpaks use dependencies all from Fedora repos.

Flathub isn’t quite default, but it’s an option in the setup screen. It’s also the lowest priority.

Fedora aims for FOSS, software unencumbered by patents, and security.

Flathub explicitly allows proprietary and patented software.

And since they want upstream apps to publish their apps and not scare them away, security isn’t as strong. Apps are allowed to use EOL runtimes and apps roll their own vendored dependencies. Fedora Flatpaks solve this problem by building all their flatpaks from their distro packages.