3 ms·
This is not quite correct. It does actually work a lot like BitTorrent. When a node loads content it begins to serve it it to other users as well. This cache ca
by tylersmith 9y ago
This is not quite correct. It does actually work a lot like BitTorrent. When a node loads content it begins to serve it it to other users as well. This cache can be purged by the user.
- dexterdog 9y agoBut isn't it fragmented so it is only serving chunks and not the whole thing?
- tylersmith 9y agoYes, data is fragmented and served in chunks just like Bittorrent. You might only serve small chunks of any given piece of data, and as a downloader you may be downloading different chunks from different peers.
- mirimir 9y agoAre the chunks encrypted or obscured? That is, could an adversary with local access to the node determine what object a particular chunk is part of? How about an adversary that can see traffic, but not the node's storage?
- StavrosK 9y agoThey aren't, how would you encrypt them so the local user could read them but someone with local access couldn't? You'd have to ask the user for a password every time the service started up, which would be terrible UX.