In this part, we will dive into the naming System of the distributed web. We will discuss it’s working, specs and play with it. We will also compare it to today’s naming system, aka the DNS. We will create a list of pros and cons of IPNS vs DNS.
In this part, we will try to understand What IPFS is, Why do we need it and What we can do with it. We will cover all the underlying components of IPFS in brief(which will be explained in depth in further parts) and see how they work together.
The go-ipfs config file is a JSON document located at $IPFS_PATH/config which is by default ~/.ipfs/config . It is read once at node instantiation, either for an offline command, or when starting the daemon. Commands that execute on a running daemon do not read the config file at
This is a quick tutorial that will teach you how to: * Host a simple static website on IPFS. * Use IPNS to keep a single id(address) when you change the content of the site * Use DNSLink to substitute the IPNS id with human-readable address Install, Initialize, and Connect IPFS to
In the last section, we learned how we can create a more resilient, censorship-resistant and faster internet using content addressing. But there are 2 problems here: * We don't want the links to our photos, websites turned into a lengthy and non-human friendly sequence of letter like this: QmPAwR5un1YPJEF6iB7KvErDmAhiXxwL5J5qjA3Z9ceKqv