Does this also apply to GNOME extensions that come pre-installed in Silverblue?
Since the Linux Overview emphasizes the importance of Wayland, it is understandable that distributions like Linux Mint with DEs that do not officially support Wayland are not recommended. However, I think Ubuntu and Kubuntu would benefit from being added to the recommendation page, along with some text about disabling/removing snapd and other disliked settings (such as suggesting which settings to disable or enable in browser recommendations).
Although unrelated to the topic, I would also like to address the confusion regarding the “Downloads” section of the apps under the “Recommendations” heading. As far as I can see, if the download pages of the apps do not include flatpak, no flatpak link is added to the “Downloads” section, but this does not seem to be the case for Tutanota Calendar and Bitwarden. I wondered why the exception was made for these two, as I see that one of them is in an experimental version on flatpak and the other is being maintained from an unverified account(s). If there is unverified maintainers requirement for flatpak and considering that Firefox is a flatpak version, flatpak links should be added for Tor Browser and Mullvad Browser.
Brave Browser does not recommend flatpak, but the official documentation for immutable distributions like Silverblue recommends flatpak first and toolbx second for installing applications. Let’s say we can install Brave Browser with toolbx, what about the Element and Signal desktop clients? From what I’ve seen on various YouTube channels, this can be done with distrobox, but you haven’t recommended distrobox layering to Silverblue.
This confusion is not only for immutable distros, but also for someone using Arch Linux for example. There are even AppImage files in the “Downloads” section of the recommended apps, but there are no instructions for installing packages from the official repositories of the distributions. Why should Arch Linux users have to deal with AppImage, extracting .tar files to a directory and then creating additional .desktop files, Flatpak, etc., when they can easily install Firefox, Tor Browser, Element, Signal, Nextcloud, Syncthing, Thunderbird, GNOME Evolution, etc. from the “extra” repository? Additionally, since you don’t recommend installing Signal and Element from Arch Linux’s “extra” repository and flatpak, it looks like we have to create a Debian or Ubuntu container from distrobox and install from the official DEB packages. Even Firefox’s help page recommends installing Firefox packages from the distros’ own repositories.
Perhaps an article should be added to the “Knowledge Base” on the conditions under which applications should be installed, and from which sources, in a secure and privacy-respecting manner.
Please tolerate my typos and grammatical mistakes.