Hacker News new | ask | show | jobs
by jeroenhd 1129 days ago
My experience is that the network works well for popular files, but if you try to share a file that's not already cached and the other service doesn't use the exact same gateway you do, you're waiting forever to browse the content.

My benchmark for this is sharing a file using the standard IPFS application and then trying to download it through either ipfs.io or Cloudflare's IPFS resolver. It usually took me about two or three timeouts before the file finally appeared and stayed available for a while. Direct IPFS to IPFS transfers using IPFS apps on both sides didn't seem to work well.

The daemons also seemed real CPU heavy for some reason.

It's a real shame, because I like the concept of the protocol. Maybe this approach of using an external, optimized pinning service wolves these problems, but that doesn't align with the goal of IPFS of course.

2 comments

I was pinning files with an inexpensive paid service, and it was pretty fast. I don't remember how well it worked when I was self-pinning. But yeah it did seem like it had some technical details to work out.
How is IPFS used in libgen?
It’s one of the sources you can use to download.