I am all for that. But we should just go there directly, not mixing events in the middle.
Let's make another protocol that is just that, give it a different name, and write different software for it.
Discussion
?cid=586b07f0p84sl86mxc6ven49zchbckk1arhfwo6i5k9j4ph3&ep=v1_gifs_search&rid=200w.gif&ct=g
there already is file sharing protocols like torrent, ipfs
we could probably build a simple hash addressed file relay system, but torrent like p2p would relieve a lot of the burden
zapping for priority service could help fund it, incentivize nodes
They both kind of suck
whats the bad points off the top of your head?
When I was trying to bootstrap dpm's codebase, I wanted to use webtorrents as a way to download files as this would be very decentralized. I couldn't even get it to download a single mb from various different servers. Same with IPFS, simply did not work.
Did you use trackers?
Was that in NodeJS? You probably just couldn't connect to the other node that had the file. No one promised automatic holepunching.
Yes. I tried uploading the file to a remote tracking service and my local qbittorrent couldn't find anything. I tried doing it on the same local network it node seeding it, qbittorrent seeding it instead, etc etc. would not work.
hypercore had really good holepunching which not surprisingly became holepunch.to
ipfs had poor holepunching but a year or so ago libp2p used by ipfs improved it quite a lot
IPFS sucks, torrents don't.