#HTTP is obsolete. It’s time for the distributed, permanent web
►https://ipfs.io/ipfs/QmNhFJjGcMPqpuYfxL62VVB9528NXqDNMFXiqN5bgFYiZ1/its-time-for-the-permanent-web.html
Part 2: How IPFS solves these problems
We’ve discussed HTTP’s problems (and the problems of #hypercentralization). Now let’s talk about how IPFS, and how it can help improve the web.
IPFS fundamentally changes the way we look for things, and this is it’s key feature. With HTTP, you search for locations. With #IPFS, you search for content.
Let me show you an example. This is a file on a server I run:
. Your browser first finds the location (IP address) of the server, then asks my server for the file using the path name. With that design, only the owner (me) can determine that this is the file you’re looking for, and you are forced to trust that I don’t change it on you by moving the file, or shutting the server down.Instead of looking for a centrally-controlled location and asking it what it thinks /img/neocitieslogo.svg is, what if we instead asked a distributed network of millions of computers not for the name of a file, but for the content that is supposed to be in the file?
This is precisely what IPFS does.
#à_lire (mais en attendant si vous l’avez lu ↓↓↓ ) ;-)
Et déjà, merci #seenthis: ▻https://seenthis.net/sites/777913 donne plein de comms intéressants :-)
