They both kind of suck

Reply to this note

Please Login to reply.

Discussion

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.

Are they keeping you isolated, Jack?

torrents definitely work with just 2 peers, it would just be your situation, torrent apps need port forwarding with nat usually, also firewalls on the machines, routers stop things

i used webtorrent with iris.to and it worked ok

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.