Bob Silverberg

> The requested change is the we do have two different pages, one for listed add-ons that aren't currently visible and another one for all remaining 404 cases. Ok, thanks...

@bhushan-borole I'm not sure that this is a good candidate for a contributor. Those issues tend to be labelled with `contrib: good first bug` and `contrib: welcome`.

@PedroFonsecaDEV Thank you for your interest. As discussed [above ](https://github.com/mozilla/addons-frontend/issues/9424#issuecomment-664513267), this really isn't a good issue for a contributor, and particularly not as a first bug. There are complexities here...

We got rid of the `core` folder awhile back, so now everything lives under `amo`. This function is still in `addons.js`, as opposed to `index.js`, but now that everything is...

I spent a lot of time on this already, and I don't plan to burn much more time on it, so I am going to remove it from the project,...

Wow, yeah, that's an old issue! Thanks @AlexandraMoga!

Reading through the old issues, I'm not sure it makes sense to re-open any of them, as they are somewhat confusing. Let's just rename this one to have it be...

This does appear to be a regression from https://github.com/mozilla/addons-server/pull/19504, which I reviewed, so I guess I should have thought to check this. addons-frontend relies on there being a valid `slug`...

Also, we currently send the `slug`, not the `guid` to the abuse reporting API, which is why it makes sense to allow front-end to continue to use the `slug` from...

> Thanks, Bob. When are you looking to land this string (i.e., what's the deadline for feedback?). > > Since this is mobile-specific, I am going to direct the question...