Rather than have the listing of add-ons in Firefox pull information down from AMO, we'd like to just reference users over to AMO if they need more information. However we can't be sure that add-on was installed from AMO or is listed on AMO. Ideally, before we bounce someone over to AMO, we should try and check that there's something to show them.
I don't understand what's covered by this that we don't already do? More specifically, check out addons.json in your profile and the "learnmoreURL" property on individual entries. This comes from the AMO API, we have bug 1402064 about updating that to a new api version but I assume we get the same information from the new api.
I think we can. It means pinging AMO through the API though. This might be the only thing that needs the API. If there's another easy or good way to do it, we might be able to remove the API ping to AMO completely.
If we want to repack extensions then we could get AMO to include the "contribute_url" and "respository_url" (or maybe a better name) in the manifest when downloaded from AMO. This could lead to an extension being installed from AMO and then it gets deleted from AMO and the link 404s, but I doubt that would be the common case.
You need to log in before you can comment on or make changes to this bug.