welcome[bot]
commented
2 years ago Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
- "Priority" labels will show how urgent this is for the team.
- "Status" labels will show if this is ready to be worked on, blocked, or in progress.
- "Need" labels will indicate if additional input or analysis is required.
Finally, remember to use https://discuss.ipfs.io if you just need general support.
whizzzkid
Severity:
Medium-High
Description:
I thought about using js-ipfs directly in the browser to share bandwidth between users, but the opposite is the case. The more peers participate, the more copies of a file a peer gets.
I created this simple example to demonstrate this issue: Example
Node0 adds the selected file. Node1 then tries to get the file. After that Node2 tries to get the file... When everything is successful, the bitswap stat "dataReceived" of each node is shown. This are the numbers for a 10.5MB file:
As you can see, Node4 receives the file 4 times.
I also did more complex tests with puppeteer, so each peer can have its own browser instance, but the results are the same.
Is there an option I'm missing or is js-ipfs just not working correctly in the browser?