Mullvad Browser is packaged as a flatpak, so it’s available on OpenSUSE regardless, but Mullvad VPN isn’t, and the files aren’t cross compatible as far as I’m aware. If it works for you, let me know so I can do it.
No, but there is significantly more community support in Arch from the AUR compared to OpenSUSE with OBS.
Mullvad Browser is packaged as a flatpak
This may be the case but generally it is recommended to not install browsers as flatpaks because it can negatively affect their built-in sandboxing.
Additionally the Mullvad Browser flatpaks is unofficial, meaning it is not maintained by the folks at Mullvad and you’ll have to trust the maintainers of this flatpak (like you have to trust Linux distribution repository maintainers).
I don’t have OpenSuse installed, though I could potentially spin up a VM of it later to test the MullvadVPN package using Fedora installation files/instructions.
Is a native installation (without Flatpak) not possible on this distribution either?
Mullvad’s .rpm didn’t work in openSUSE without modifications, but now it does, at least on Leap16. I don’t know for Tumbleweed
It is possible via the third party RPM repository provided for Fedora by Mullvad.
However at this point I think the discussion of whether or not we can install Mullvad VPN and Mullvad Browser has gotten a little off topic from the original question in this thread of if a warning on the recommendations for NixOS or OpenSUSE is something Privacy Guides should consider since some packages may not be available out of the box on those distributions.
I’m not sure how we would go about getting a change like this implemented though. I’m unfamiliar with the process.
If you are referring to the process for getting a “warning” approved for the Privacy Guides OS - Desktop/PC as described in the above quote, then we are already in the right place since this topic thread is already under the Site Development category.
Yes, but now what? Do we just wait for a moderator to read it and think its a good idea?
More or less yes.
Well that seems inefficient.
It would probably help if it receives a few votes.
Do you have some advice to improve?
Maybe consensus within a thread should lead to the thread author creating a feature request or submitting a pull request on GitHub - privacyguides/privacyguides.org: Protect your data against global mass surveillance programs. · GitHub
Vote count / threshold? Like if x users agree it gets implemented or if there’s like a 2/3 consensus?
If a Site Development post gets more community votes it is more likely that the Privacy Guides team will look at/and make a decision on the topic, but it is not a guarantee of anything.