Release on addons.mozilla.org

[ruihildt]

This was planned, but no tracked.

We need to release it on https://addons.mozilla.org in order to enable auto-update for users.

[ruihildt]

@carbongreat13 We plan to host the auto-updates on our servers, would that solve your issue? Or is there a more specific reason why you would like to have the extension on AMO (addons.mozilla.org)?

[kalekad]

If the extension were on AMO, it would be possible to install it on Firefox for Android.

[Victor239]

Another reason to have it on AMO is so that regular Firefox desktop users can install it. Mullvad Browser is my secondary browser rather than primary due to limitations like permanent Private Browsing mode so it'd be good to have the extension available in both browsers.

[ruihildt]

Another reason to have it on AMO is so that regular Firefox desktop users can install it. Mullvad Browser is my secondary browser rather than primary due to limitations like permanent Private Browsing mode so it'd be good to have the extension available in both browsers.

@Victor239 You can install it in any modern Firefox based browser from this page: https://mullvad.net/en/download/browser/extension

[Victor239]

Ah I see, I didn't see a link in the README so I thought the only way was the temporary install.

[ruihildt]

Ah I see, I didn't see a link in the README so I thought the only way was the temporary install.

Good point, I'll make it clearer. Temporary install is only if you develop the extension.

[begin-theadventure]

I think the add-ons store could be more trustworthy and accessible for some people, it also has reviews.

But anyway, what's the reason that you want to host it on your site instead of just releasing it on the official add-ons site?

[ruihildt]

But anyway, what's the reason that you want to host it on your site instead of just releasing it on the official add-ons site?

In terms of security, it has no impact since it anyway needs to be signed by Mozilla.

The only reason to keep it outside of AMO would be if we wanted to diverge the code between what's shipped in Mullvad Browser and what's available in AMO.

We don't have such plan at the moment, so I think we may keep both for some time, and then see where we're at in the future.

[git70]

I'd like to add my two cents to the decision:

1. The most common workflow of users and the strength of habits are also important.
2. Compliance with the general philosophy of using repositories in the FOSS world. It concerns:
   • support for Firefox extensions via AMO
   • create a deb repository for the main MullvadVPN application, which the user can add to his sources.list and operate according to the workflow (not a PPA, but a regular repo that will serve both Debian and Ubuntu users and derivatives)
   • adding Mullvad Browser to Flathub

Why do you avoid solutions recognized as standard in the Linux environment so much?

[ruihildt]

@git70 We plan to add it to AMO, it has just not been prioritized.

I can also answer for the Mullvad Browser: we are looking at packaging options and what we're able to maintain.

[git70]

This is great information!

Please also seriously consider repo for mullvadvpn-app. This will really make a lot of users happy, and there's nothing better than a happy user ;)

In addition, pay attention to one more important aspect as an argument for the system repo: Speed ​​and automatic distribution of important patches (if necessary). People are set to check for updates every few hours...voila!

[ruihildt]

I can't speak for the app team, but I see you've already been active in https://github.com/mullvad/mullvadvpn-app/issues/3049. ;)

[git70]

I patiently fight as much as I can for the right ideas and a better world ;)