Dylan Powers

@hosh I can go ahead and run through these for you

@hosh In 005 I got to step 4 and when running make I got the following error: ``` $ make mkdir /ipns/local/docker-registry Starting docker-registry on ipfs if it is not...

Oh boy it's been a long time since I played with IPFS :open_mouth: I'd be happy to accept a pr or let someone else take ownership of this small piece...

FWIW Chrome does allow matching paths so the performance impact would be pretty limited and not as bad as the dns redirects https://developer.chrome.com/extensions/match_patterns

Note that this extension does support inputting urls in the form `/ipfs/Qme3pKkedCfcebDmkZz5tU2suMjHP4EPi29NMNNxQrQzwy/done`. You just have to click the "Allow access to file URLs" option on the chrome://extensions page

Derp, just call into the ipfs dns api off of port 5001

Just need to add another line with https at https://github.com/dylanPowers/ipfs-chrome-extension/blob/master/ext/main.dart#L337 Should also change https://github.com/dylanPowers/ipfs-chrome-extension/blob/master/ext/main.dart#L276

Does IPFS Station have all of the same functionality as this extension?

I'll have to look into it then. I don't really have any interest in maintaining this and if the IPFS Station extension does everything this does I may deprecate this...

Ideally, all requests will never go to computers the user doesn't have control of. Currently it doesn't because I trust gateway.ipfs.io and the networks my requests are going through to...