When you share say an 5MB mp3, with the default x10 oversharing, you’ll negotiate with 10 other nodes to “you share mine, I’ll share yours”.
The system will (configurable) accept files up to twice that size. It will statistically even out to roughly the same size of your file x the oversharing.
And don’t forget, we’re not talking about TB of data, but Megabytes. You can “lose” some space quite many times before even hitting a Gigabyte. A GB is not much today, or so I think.
When you decide to update your mp3 (say you have a “song of the day”) then all nodes will get an update request. If they fail to update, they’ll just be dropped and a new node searched for. You can also just clean out the shares if you want to, they’ll repopulate automatically.
With oversharing, you just need one of them all to be ‘up’ to make the system work, you can share your new song, shut your PC down and it still works.
How does it handle website updstes to smaller size or loss of host? Will the network “forget”/discsrd the old/uncovered version/data sutomstically?
When you share say an 5MB mp3, with the default x10 oversharing, you’ll negotiate with 10 other nodes to “you share mine, I’ll share yours”.
The system will (configurable) accept files up to twice that size. It will statistically even out to roughly the same size of your file x the oversharing.
And don’t forget, we’re not talking about TB of data, but Megabytes. You can “lose” some space quite many times before even hitting a Gigabyte. A GB is not much today, or so I think.
When you decide to update your mp3 (say you have a “song of the day”) then all nodes will get an update request. If they fail to update, they’ll just be dropped and a new node searched for. You can also just clean out the shares if you want to, they’ll repopulate automatically.
With oversharing, you just need one of them all to be ‘up’ to make the system work, you can share your new song, shut your PC down and it still works.