com.brave.Browser VS org.ardour.Ardour

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

Ardour https://github.com/flathub/org.ardour.Ardour/blob/master/org.ardour.Ardour.json#L564 - it checks out the Ardour git repo at a specified commit and adds a patch changing an identifier (https://github.com/flathub/org.ardour.Ardour/blob/master/patches/ardour5-5.12.0-appdata-flatpak.patch).

Having checked the screenshots I see you're running Ardour from a flatpak. Flatpaks may not be able to see outside their own internal file system (e.g. the notes at https://github.com/flathub/org.ardour.Ardour say "You cannot install or use plugins not packaged as a Flatpak. ").