-1

Why is it so hard for web browsers to open IPFS links?

For instance, this is an IPFS blog page link, https://ipfs.io/ipfs/bafybeic3y6oc2dai3uypyyuaggp4xx3krocpgzbwst2z4ha73jdh7y6nea/index.html , and the loading page is tremendously slow on Safari or Chrome/Edge, and it's stuck into Error 504 from time to time. Is there any way to browse IPFS pages smoothly? Or are IPFSs just internally incapable of smooth browsing without third-party helps?

Xavier Xie
  • 1
  • 1
  • Considering the amount if things happening in the background (cryptographically, logistically), the page loaded decently quick for me. It's in the nature of p2p to load blocks faster that are available on more nodes that are well known and widely distributed. – Daniel W. Oct 21 '22 at 21:15
  • 1
    The reason why the objects are maybe loading slow from `https://ipfs.io` might be because that public page has a lot of traffic. You can setup your own client/proxy/api and try that instead: https://docs.ipfs.tech/reference/ – Daniel W. Oct 21 '22 at 21:31
  • Wondering if there are other public gateways for ipfs that is not ipfs.io ? – Blissful Oct 26 '22 at 14:04

1 Answers1

0

You're loading the page through a gateway. So effectively, you're asking another (quite popular) IPFS node to fetch the info over IPFS, then serve it to you over HTTP. If the gateway is slowed down for any reason, all IPFS resources will seem slow to you. If a gateway is your only option for whatever reason, check out the IPFS Gateway Checker for a list of active ones.

Alternatively, you could run your own IPFS node via something like IPFS Desktop then connect it to IPFS Companion (Chrome | Firefox). IPFS Companion can be configured to redirect all IPFS gateway links to your own IPFS node, then you'll be limited by just how quickly your node can find/retrieve the data, which you'll likely find to be the superior IPFS experience.

The Brave browser also includes an integrated IPFS node. They have an article about it here.

Discordian
  • 749
  • 3
  • 16