What is the default gate?

Help Old FAQ
1

From @Mithgol on Thu Sep 17 2015 07:00:29 GMT+0000 (UTC)

Should I direct people to http://gateway.ipfs.io/(ipfs|ipns)/$RESOURCE when they haven’t (yet) configured their local IPFS installations? Or would http://ipfs.io/(ipfs|ipns)/$RESOURCE (without gateway.) always suffice? (As it does now.)


Copied from original issue: https://github.com/ipfs/faq/issues/42

2

From @lgierth on Thu Sep 17 2015 08:10:44 GMT+0000 (UTC)

Direct them to ipfs.io – gateway.ipfs.io is deprecated and will start redirecting to ipfs.io soon. We won’t shut it down though, for the foreseeable future.

3

From @Mithgol on Thu Sep 17 2015 09:16:12 GMT+0000 (UTC)

I hereby summon @lidel because the README of https://github.com/lidel/ipfs-firefox-addon/ seems to indicate that only gateway.ipfs.io is supported (i.e. replaced) by that addon.

4

From @lgierth on Thu Sep 17 2015 10:19:06 GMT+0000 (UTC)

Yep that should be updated

5

From @lidel on Thu Sep 17 2015 11:18:57 GMT+0000 (UTC)

Good catch. I updated README to cover old and new URLs.
The addon already supports https://ipfs.io/(..)

6

From @Mithgol on Thu Sep 17 2015 11:35:46 GMT+0000 (UTC)

I hereby summon @dylanPowers because the README of https://github.com/dylanPowers/ipfs-chrome-extension/ seems to indicate that only gateway.ipfs.io is supported (i.e. replaced) by that Chrome extension.

7

From @jbenet on Thu Sep 17 2015 16:19:24 GMT+0000 (UTC)

@Mithgol things get outdated. Submit a PR to fix it, or open issue there

—
Sent from Mailbox

On Thu, Sep 17, 2015 at 7:35 AM, Mithgol notifications@github.com wrote:

I hereby summon @dylanPowers because the README of GitHub - dylanPowers/ipfs-chrome-extension: Access gateway.ipfs.io urls the way they were meant: from your locally running ipfs daemon seems to indicate that only gateway.ipfs.io is supported (i.e. replaced) by that Chrome extension.

Reply to this email directly or view it on GitHub:
What is the default gate? · Issue #42 · ipfs-inactive/faq · GitHub