search

internetarchive / dweb-transports

GNU Affero General Public License v3.0
25 stars 16 forks source link

Adding "seed" #18

Open mitra42 opened 5 years ago

mitra42 commented 5 years ago

I'm working on adding "seed" as another supported function - the design thinking is in dweb-mirror#117 which is the first use case.

@rodneywitcher - particularly interested in how we might want this to work with Wolk as well. I think it would involve adding keys during config, but not sure what info needs passing during the request to seed a file or directory.

mitra42 commented 5 years ago

seed is added in TransportIPFS and Transports

rodneywitcher commented 5 years ago

@mitra42 -- can you clarify what you mean by seed a file directory? Is this just in reference to storing a dfor retrieving or both? Also, can you give more detail on what you mean by seed? Is this the equivalent to "signing" a request?

mitra42 commented 5 years ago

Seeding is not the same as adding, it is about taking a file and participating in the P2P, at the moment I've implemented it in IPFS and WebTorrent, (typically file retrieved by HTTP and then cross-seeded to IPFS/WT) in those cases the file is immutable, so there is no requirement to sign it - i.e. the address is the signature, so any peer can reinsert into IPFS/WT safely. Its particularly useful where the network is segmented, e.g. a file retrievd via HTTP then inserted via WT for access in the local network. Or behind a censorwall would also be useful. In Wolk that might not work because the signature would have to come from the originator, and there is a payment step, and I'm presuming that if Wolk can find the signature then its already got the file ?