IPFS — Inter-Planetary File system

A for-life, decentralised, privacy respecting web.

Imagine a web where no one can track you. No one can delete you. No censorship. No big brother. No Evil corp.

It sounds like a dream.

IPFS is the idea that makes this dream possible. RIGHT-NOW.

Here, let me show you:

maximveksler$ ipfs cat /ipfs/QmVtU7ths96fMgZ8YSZAbKghyieq7AjxNdcqyVzxTt3qVe/about
IPFS — Inter-Planetary File system
IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bit-torrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence built in. You can also mount the world at /ipfs.

See, it’s just a file system. How harmless can a file system be?

IPFS is a protocol:
- defines a content-addressed file system
- coordinates content delivery
- combines Kademlia + BitTorrent + Git

Actually IPFS is a protocol, and as such it enables new models of collaboration between devices, systems, people and communities.

IPFS is a web:
- can be used to view documents like the web
- files accessible via HTTP at `http://ipfs.io/<path>`
- browsers or extensions can learn to use `ipfs://` directly
- hash-addressed content guarantees authenticity

It enables a web. THE web was envisioned as a globally accessible hyperlinked collection of resources. Our tools will learn to speak ipfs:// the same way they know today about http:// making the web be just one of the use cases.

IPFS is modular:
- connection layer over any network protocol
- routing layer
- uses a routing layer DHT (kademlia/coral)
- uses a path-based naming service
- uses bittorrent-inspired block exchange

It’s obstacle aversive much in the spirits of the Internet’s original design. Keeping you out of the information will psychically require to isolate you from any communication method with the outer world.

IPFS uses crypto:
- cryptographic-hash content addressing
- block-level deduplication
- file integrity + versioning
- filesystem-level encryption + signing support

It trust encrypted. A CPU will ensure that no wishful thinking government will be able to temper with the validness of the content you are reading. It is in essence having our devices work for us.

IPFS is p2p:
- worldwide peer-to-peer file transfers
- completely decentralized architecture
- **no** central point of failure

It’s about the people. You don’t need a corporation to run it, just a bunch of like minded peers. United.

IPFS is a cdn:
- caching-friendly (content-hash naming)
- bittorrent-based bandwidth distribution

It’s efficient. It respects your time. Based on the principles of physical distance and virtual bandwidth, the information will be downloaded from the nearest possible, fastest resoufce available.

IPFS has a name service:
- IPNS, an SFS inspired name system
- global namespace based on PKI
- serves to build trust chains
- compatible with other NSes
- can map DNS, .onion, .bit, etc to IPNS

It’s compatible. Meaning it can theoretically, as a side project also rid the world finally of the troubles of centralised domain management troubles as well.

From a bottom line perspective

IPFS shifts us from the deterministic world of either something works or it doesn’t into the highly available, rarely partially available and possibly dead modelling of computer systems, which carries greater similarity to how real life works. Our computers should be designed to handle this fuzzy logic at their core and this to my view is a step at this very promising direction.

The revolution will be Merkle DAG’ed

Mind blown ✌️

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.