DEFAULT IPFS GATEWAY
ONION IPFS GATEWAY
3rd PARTY IPFS GATEWAY
OPEN IN NEW WINDOW
OPEN IN LOCAL WINDOW
NOT INDEX CONTENT
What is IPFSGate
The IPFSGate is an advanced public IPFS gateway, IPFS websites provider and IPFS storage. You can use the gateway to access the content located in the IPFS network directly from your web browser without installation of any software or plugin. You are allowed to browse any IPFS content via our default IPFS gateway or you can select from many 3rd party IPFS gateways. Those of you who use Tor Browser for a better anonymity can take advantage of Onion IPFS Gateway (IPFS over Tor network).
IPFS Blog » Articles« Back to articles overview
IPFS web hosting
So where is the problem? Why don’t we see thousands of successful websites hosted content in the IPFS ? Why don’t we see decentralized e-commerce platforms offering all kinds of an illegal services including warez, drugs and weapons? Why although the IPFS is an awesome tool to make world more decentrallized and full of freedom, it lacks the practical implementation ?
Main reasons for this are as follows and will be discuss below:
- IPFS content immutability
- Too many resources per single page
- IPFS “does not know” the backend part
- Our society does not want to be decentralized yet
IPFS content immutability
IPFS content is immutable. Any change in content provides different CID. It means that any changes on your web provides different CID = “different URI” to access to your web. From this point of view the IPFS is suitable only for static content. If you make any changes in your content, you have to ensure that your customers gets new CID every time. To solve this, the solution can be the use of IPNS instead of IPFS, or store current CID on ethereum blockchain (ENS). These approaches were discussed many times earlier and we will not it discuss here.
Too many resources per single page
This issue may not be so obvious, but results in that there is much more difficult to effectively run websites in the IPFS than one could think. We think that it is the reason, why websites and IPFS e-commerce platforms are not spread yet. Let me explain it:
IPFS “does not know” the backend part
Everything in IPFS is frontend. Natively, IPFS does not know the backend part. There are two ways to solve it. If we consider the backend part only the database of our application, then JSON or XML files stored in the IPFS network can be used for this purpose. It is the same solution that was discussed in the paragraph above. In the case when we need a full-fledged backend part of the application, it can be solved by separating the frontend part of the application (which runs in IPFS) and the backend part of the application, which run outside the IPFS. The front-end part of the application can send/retrieve data e.g. by AJAX. However, in this case it is clear that the backend part of the application is not decentralized and can be easily censored or shut down.
Our society does not want to be decentralized yet
IPFS is an excellent tool for the society who wants to be decentralized. But does our society wants to be decentralized? I am not sure. Ask people around you what censorship-resistant tech they know. Probably the most people tell you the Tor network and the Bitcoin and adds that both should be prohibited, because it supports an illegal activities. And those same people then screams loudly when the restriction of freedom touches their needs. Many people do not yet realize that our society has reached a tipping point where it is incredibly easy for a very small group of people (e.g. government) to censor, rule and control people around the world, set what is right and what is wrong. We believe that IPFS is a tool that can bring pepole freedom and will teach them to be responsible for themselves.