Mathieu Pillard

> We could change the API to always return a dict (with only the requested locale, or the default locale otherwise) That would be my preference, because more query parameters...

This likely caused https://github.com/mozilla/addons/issues/14677

QA: Let's just test that this hasn't accidentally dropped existing usernames that were not dupes by loading known public collection URLs like https://addons-dev.allizom.org/en-US/firefox/collections/VictorQATester/testcollect/ and making sure they still work.

Actually, the new migration initially didn't take on stage, it failed with: `ERROR 1062 (23000) at line 7: Duplicate entry 'anonymous-83f2f3c3aefa9a786cee930e3572eba932' for key 'username'` The relevant SQL was this: ```sql...

> (is it the `UPDATE` or the `ALTER` that follows it ?) It's the `UPDATE`, and it's now finished. We don't know how much more than 7 hours it took,...

And https://github.com/mozilla/addons/issues/6974 has the history of issues with option 3 (Tl;DR: we could go with the nuclear option and delete most non ascii usernames to solve the conflicts, or try...

Do we have requests to URLs with usernames (instead of user id), and if so which ones, and how many ? Let's look for requests matching these in the logs:...

This is something I overlooked in https://github.com/mozilla/addons/issues/8830 - when we submit using addon `guid` or `slug` (or even `id`), we don't send the add-on name. When displaying the reports, we...

I've asked in the PRD but @jvillalobos you can comment here if you prefer.

We do have URLs in place but I avoided exposing this in the API until now because of the platforms mess. When the add-on file is available for all platforms...