Hey @smwa

I'm not sure where your issues with IPFS come from - but I'm sure we can work them out. :)

I got an idea of how to "just" have the bandwidth, without having to store the whole archive of files in your IPFS-Node:

Librivox can be found on archive.org. They have static web-url for all files. So we could setup a ipfs node and add all URLs via URL-Store:

ipfs add --nocopy https://archive.org/download/girl_boat_1109_librivox/girlboat_01_wodehouse.mp3

This command will fetch the file from the URL, calculate the CID, store the URL in your database, but won't store the actual file there.

Your node will (try to) fetch the file from the URL every time someone on the IPFS network site requests it.

This way we don't have to keep a copy of the actual data, only the metadata, but also guarantee that the file is intact when it's sent to the IPFS-network.

We can also generate a list of all URLs and CIDs and put them in a cluster in the long run.

This will have the other cluster members download the whole file and store them, while your server will just provide the download-source.

When running catalog/fetch.py in python 3.7.6 I receive an error:

OSError: [Errno 24] Too many open files

Currently, the website seems to be completely broken. Via local gateway, the download will terminate after some minutes. Via an HTTP gateway, the download will terminate right away with a "not online" error.

Hello,

I notice that the HTTP version of site resolves to https://ipfs.smwa.me/ipns/wistfulbooks.com/

This seems dead.

Can you update it to a live gateway?
Perhaps on of the following would work:

• https://ipfs.io/ipns/wistfulbooks.com/
• https://gateway.ipfs.io/ipns/wistfulbooks.com/

There is a whole list of live IPFS public gateways at:
https://ipfs.github.io/public-gateway-checker/

Thanks for everything!