Mathieu Pillard

> Old URL with the app would need to continue to work... we used to redirect in the other way around (no app redirects to with app) so that might...

We could start by not consolidating the `/android/` and `/firefox/` paths into one and focus on tackling the CDN behavior instead. That would likely mean having the 2 patterns separate...

This is still valuable - it would improve our cache hit ratio, therefore consuming less bandwidth - but we should wait until we've switched away from CloudFront.

That's not a new issue, right ? I assume this is because when the abuse report is sent by Firefox internal mechanism, it doesn't pass the authentication info from AMO....

This happens because the Abuse Reports sent by Firefox don't use the cookies the user has on AMO at submission time. The thing is, I'm not sure we want to...

This was fixed by https://github.com/mozilla/addons/issues/14807 (note that you need to set `extensions.addonAbuseReport.url` on dev/stage, it defaults to prod)

Also something I noticed on the triumvirate of slow uncommon pages: https://github.com/mozilla/addons/issues/14129, https://github.com/mozilla/addons/issues/14130, https://github.com/mozilla/addons/issues/14131. For instance, the Dictionaries and Language Packs page is around 26K gzipped, 12K of it is...

I'm not sure we should focus on optimizing which API bits we need or not. This is unlikely to have that much impact, the permissions thing is an outlier, that...

It's already a p4, we can leave it and let stalebot close it eventually if we haven't had the time to revisit this.

While we're at it the `MOZILLA_NEWSLETTER_URL` setting is defined but appears to be unused and should be removed.