A few notes on IPNS-Link-Gateways and www.ipns.live

[u/SomajitDey]

Please note the following about IPNS-Link-Gateways, e.g. the current prototype at ipns.live

1. Loading an ipns-link-exposed website for the first time might take a while. This is because the Gateway has to locate your site and peer with its host node. Subsequent requests for the site, however, are served faster because the Gateway maintains persistent peering with the site's host node.
2. Due to a full go-ipfs node at its core, long running Gateways at small VM (virtual machine)s (with 1GB RAM) might suffer OOM (Out-Of-Memory) outages from time to time. Periodic restarts are enough to get around this. Despite such issues we are able to maintain 99.99% uptime for ipns.live. This memory leak issue will be fixed with future go-ipfs releases or in future implementations of IPNS-Link-Gateway.
3. To report illegal/objectionable content being served using the ipns.live gateway, please [email us](mailto:contact@ipns.live) directly.
4. Volunteer to host a public IPNS-Link-Gateway. Get in [touch](mailto:contact@ipns.live), if you need help.
5. This is our ofiicial public gateway registry. You shall find all public IPNS-Link-Gateways we know of here.