Question: What are the usage guidelines for the IPFS Gateway?
I have been communicating with a variety of projects and we have come to a conclusion that we would like to make our website not only accessible, but also hosted on IPFS.
The reason for this is that many of them already use GitLab Pages.
We want users to be able to verify every piece of our source code.
For us, it makes a lot of sense to use a trusted gateway and we would like to use IPFS’s gateway at 22.214.171.124 to host our webpages. However, we wanted to make sure their are no guidelines prohibiting this by protocol labs or affiliates.
TL;DR Does IPFS have any rules or guidelines for the usage of their gateway service?
That’s great! The gateway can be used for hosting websites. The official ipfs.io gateway is run as a public service that provides a general purpose http-to-ipfs upgrade path for tools that don’t speak ipfs yet, and for folks to experiment with content-addressing and the dweb.
IPFS does not have published usage guidelines for the gateway yet. We will be publising one by the end of the year. In the meantime, the IPFS community Code of Conduct applies to all content served over the official ipfs.io gateway.
Other http-to-ipfs gateway providers are available. Every IPFS deamon runs it’s own gateway, so you can host your own, or you can try out any of the hosted ipfs services, see: https://infura.io/ and https://pinata.cloud/ and https://www.eternum.io/ and others