Commit c31a1cf193301a1dc31cad31298b9f3f0b329a44
Update README.md
William Blankenship authored on 12/21/2017, 9:00:46 PMGitHub committed on 12/21/2017, 9:00:46 PM
Parent: 4c2751adfecf7c5284c97e4ec8a7ce2767b8f4b9
Files changed
| README.md | changed |
| README.md | ||
|---|---|---|
| @@ -7,11 +7,11 @@ | ||
| 7 | 7 … | ## If websites are hosted on p2p, what happens when no peers are online? |
| 8 | 8 … | |
| 9 | 9 … | Many p2p systems, i.e. BitTorrent, are optimized for sharing popular content. The more popular a piece of content, the more available the content becomes. The less popular content is, the less available the content becomes. Popularity in this case is the number of peers actively consuming and sharing a piece of content. The ability to access any piece of content on a p2p network is limited by the availability of peers, no peers no content. |
| 10 | 10 … | |
| 11 | -If you share content on a p2p network that you have a vested interest in being always-available, you must invested in maintaining your own highly available peers that share this content. This is not dissimilar to a centralized network, in that you must build highly available infrastructure to share your content. However, unlike a centralized network, you're infrastructure is no longer a single point of failure since you have the benefit of a p2p network supporting you. | |
| 11 … | +If you share content on a p2p network that you have a vested interest in being always-available, you must invest in maintaining your own highly available peers that share this content. This is not dissimilar to a centralized network, in that you must build highly available infrastructure to share your content. However, unlike a centralized network, you're infrastructure is no longer a single point of failure since you have the benefit of a p2p network supporting you. | |
| 12 | 12 … | |
| 13 | -In the p2p model, you are not soley responsible for your uptime or performance. If your system falls over, there is still a chance for consumers of your content to fetch from another peer. If there is a spike in popularity of your content, peers will share content amongst eachother reducing the burden on your infrastructure. In many cases this can provide a better overall experience for consumers of your content. | |
| 13 … | +In the p2p model, you are not soley responsible for your uptime or performance. If your system falls over, consumers of your content can still fetch from another peer. If there is a spike in popularity of your content, peers will share content amongst eachother reducing the burden on your infrastructure. In many cases this can provide a better overall experience for consumers of your content. | |
| 14 | 14 … | |
| 15 | 15 … | ## What about security? Somebody could share a hacked version of a p2p website? |
| 16 | 16 … | |
| 17 | 17 … | ... |
Built with git-ssb-web