{"action":"opened","issue":{"url":"https://api.github.com/repos/nolanlawson/local-npm/issues/88","labels_url":"https://api.github.com/repos/nolanlawson/local-npm/issues/88/labels{/name}","comments_url":"https://api.github.com/repos/nolanlawson/local-npm/issues/88/comments","events_url":"https://api.github.com/repos/nolanlawson/local-npm/issues/88/events","html_url":"https://github.com/nolanlawson/local-npm/issues/88","id":126912807,"number":88,"title":"Incorrectly assumes that the --remote repo is another local-npm","user":{"login":"nolanlawson","id":283842,"avatar_url":"https://avatars.githubusercontent.com/u/283842?v=3","gravatar_id":"","url":"https://api.github.com/users/nolanlawson","html_url":"https://github.com/nolanlawson","followers_url":"https://api.github.com/users/nolanlawson/followers","following_url":"https://api.github.com/users/nolanlawson/following{/other_user}","gists_url":"https://api.github.com/users/nolanlawson/gists{/gist_id}","starred_url":"https://api.github.com/users/nolanlawson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nolanlawson/subscriptions","organizations_url":"https://api.github.com/users/nolanlawson/orgs","repos_url":"https://api.github.com/users/nolanlawson/repos","events_url":"https://api.github.com/users/nolanlawson/events{/privacy}","received_events_url":"https://api.github.com/users/nolanlawson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-01-15T17:00:31Z","updated_at":"2016-01-15T17:00:31Z","closed_at":null,"body":"Follow-up to https://github.com/nolanlawson/local-npm/issues/84: we need a better way to detect whether the `--remote` repo is another local-npm or not, otherwise e.g. if someone has an HTTP proxy to the main npm, then we will assume it's `local-npm` and be unable to fetch tarballs. The current system for detecting this is hacky and is based on looking for a URL that looks like `https://registry.npmjs.com`.\r\n\r\nWhat we should do is first do a `GET` request to the fat registry and check if it sends back some piece of information to identify it as `local-npm` (I think local-npm already does this, just for convenience). This could be done in the setup, along with the `info()` operation on the skimdb."}}