Which esp32? There are so much options nowdays!
fermuch
joined 4 years ago
After re-reading my comments, I thought they might come as aggressive. That's totally not what I mean!
Congrats on launching the project! My comments here are to address what might be common problems in a p2p network, to see your POV on these problems, and maybe give you ideas on points you might want to research in the future.
As far as I know, this is the first "distributed" and "easy-to-use" tool we have. I've never seen something as easy as 10f -i file.jpg and share it!
But there are some prior attempts for mostly-related ideas, which could be:
- Online file sharing (MEGA, MediaFire, Imgur, even Dropbox...)
- P2P networks focusing on file sharing like i2p or freenet
For online file sharing, some recurrent problems are: DMCA. How do you (an operator of the network) handle a DMCA request?
And for P2P networks, the focus always is: how can I ensure I do not host illegal files? Even if they are encrypted, some legislation still can consider it as keeping illegal files (AFAIU).
Thanks for the quick answer!
If you want to share a 1MB website (which is quite big IMO) and share it 10 fold, you'd need roughly a whopping 11MB of storage.
Is it possible to be a "hoarder", and keep storage for others without adding new files?
How do files expire? Is there a last-activity expire, random keys expiring or something like that?
Are there "scores" for peers? If I contribute 1TB of storage but am online only 2 hours a week, am I penalized in some way (like lower trust)? If so, how do you verify that?
And what about data locality? Is there any kind of incentive to have data located closer to where it is most used? (Like a cdn)
Finally: if there is a peer scoring system, is bandwidth part of the calculation too? For example: a peer with just a few gigabytes, but 1gbps network to share. Would they receive a better score because of their network? Or worse because of their low storage?
Using a strong incentive to share.
What would that incentive be?
Possible to modify your shared data or your computer address (IP:PORT) without the need to re-distribute the link.
How would you handle spam if the content can be updated?
Accessible to anyone who can spare some disk space and some bandwith
What about mobile users, who have a data plan limit, low space and battery to worry about (so no daemon 24/7)?
Have you done any Thread/Zigbee with an esp32? I cannot wait to get a C6 to test it!