Vincent

Thanks for the suggestion! Since this suggestion relates to the extension, I'll move it to that repository so that it gets tracked where it's relevant. Btw, note that while it's...

Hi @pendantry, this is expected behaviour, and it's one of the reasons why we recommend using random (non-subdomain) aliases whenever possible. The intended use case for subdomain aliases is when...

Thanks @pendantry, I relayed (:drum:) your comments to the team, so it will serve as input as we consider how to deal with this going forward. Thanks for sharing! Edit:...

Thanks for the report @pascalchevrel. This is an issue with the extension, so I've moved it to the extension's repository. Meanwhile, note that you don't need to disable the extension...

The add-on has access to [`runtime.getBrowserInfo`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/getBrowserInfo) and [`runtime.getPlatformInfo`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/getPlatformInfo), but I think the backend will need an update to accept that data.

Hi @pendantry, I'll pass your confusion back to the designer, but to answer your questions: 1. It is recommended to use the `@mozmail.com` domains when you can, because they cannot...

Yep agreed, I brought up that exact suggestion with the team :)

Appears to be an add-on issue, so moved to that repo. Fix incoming.

@lquixada I can confirm that it fixes it for my project!

No worries @eemeli, hope you enjoyed your travels :) Yes, you are correct about the approach I took. I understand the desire for a single internal implementation, but I'm hesitant...