Commit 6d0b851543b8ebf2bf92a7a3f0c4b438f2e4163b
notes on availability
Stephen Whitmore committed on 1/6/2018, 4:08:28 AMParent: 969e1e16e2a878f61b1955976fa3f61e943e8e9a
Files changed
| README.md | changed |
| README.md | |||
|---|---|---|---|
| @@ -17,10 +17,17 @@ | |||
| 17 | 17 … | that torrent data to be served grows exponentially. | |
| 18 | 18 … | ||
| 19 | 19 … | ## If websites are hosted on p2p, what happens when no peers are online? | |
| 20 | 20 … | ||
| 21 | -... | ||
| 21 … | +The same result as when a centralized website goes down: it isn't available. | ||
| 22 | 22 … | ||
| 23 … | +The difference is that peer-to-peer networks distribute *the power to host*. I | ||
| 24 … | +could run a peer serving my website on a server. Instantly I have the same | ||
| 25 … | +website availability as a traditional centralized website. The difference is | ||
| 26 … | +that there may be many peers in the swarm that are also hosting my website, so | ||
| 27 … | +if my server goes down, the site will continue to be accessible through those | ||
| 28 … | +seeding peers. | ||
| 29 … | + | ||
| 23 | 30 … | ## What about security? Somebody could share a hacked version of a p2p website? | |
| 24 | 31 … | ||
| 25 | 32 … | ... | |
| 26 | 33 … | ||
Built with git-ssb-web