com.brave.Browser VS io.mpv.Mpv

Currently, the package brave-keyring is responsible for updating the key. However, solutions based on cron and at are not only ugly but also not expected to work in openSUSE Aeon (formerly openSUSE MicroOS Desktop). Someone else has already reported a similar issue with Fedora Silverblue and Fedora CoreOS (https://github.com/brave/brave-release/pull/28). (The preferred alternative for these distros is the Flatpak package, but it doesn't seem that a fully official release will appear quickly https://github.com/flathub/com.brave.Browser/issues/137).

Brave is not in the 22.04 repos, but it has both a flatpak and a snap

If you're not using the flatpak version, does that version have the same problem?

Is that the Flatpak version? I think it's safe. It's from flathub.org (https://flathub.org/apps/details/com.brave.Browser) so it must be curated software.

At times this tool is utilized to grant a flatpak more permissions; to enable a specific use case. For example to enable 'communication' between KeepassXC and Brave/Librewolf for proper browser integration.

netflix should work through your default web browser, if not you may want to try https://flathub.org/apps/details/com.brave.Browser

Submitted a PR for the flathub build: https://github.com/flathub/io.mpv.Mpv/pull/164

For MPV, there are a lot of other libraries/applications used/included with it and that's what's being updated (not MPV itself). You can see the changelog here.

Note that the config directories paths differ with the flatpak version, as mentioned here:

According to https://github.com/flathub/io.mpv.Mpv/blob/master/io.mpv.Mpv.yml, it does pass --enable-libdav1d to ffmpeg's build script, but it never fetches any code from dav1d's git repository? Really weird, not sure if it's an oversight from the maintainer or something else.