We originally used pin.valist.io as our hosted IPFS infrastructure. Since then, we switched to using estuary and proxying authenticated requests to their servers.
However, by relying solely on estuary infrastructure, there's 3rd party risk. DHT discovery can also be slower than if we provided our own nodes + bootstrap peers.
We'll need to re-architect this a bit so that estuary is backing up our 1st party IPFS nodes, and using pin.valist.io as our default pinning remote, as well as include the peers in the bootstrap list on the client.
We originally used pin.valist.io as our hosted IPFS infrastructure. Since then, we switched to using estuary and proxying authenticated requests to their servers.
However, by relying solely on estuary infrastructure, there's 3rd party risk. DHT discovery can also be slower than if we provided our own nodes + bootstrap peers.
We'll need to re-architect this a bit so that estuary is backing up our 1st party IPFS nodes, and using pin.valist.io as our default pinning remote, as well as include the peers in the bootstrap list on the client.