You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the automatic content routing based discovery finds no providers/candidates.
So I have to add manually additional --providers value which are not on DHT or cid.contact.
Unfortunately, this disables automatic content routing based discovery.
It would be very helpful if I could define via CLI when adding one or more –providers value that the that the automatic content routing based discovery remains activated.
The definition of the discovery sequence would also be very helpful:
first automatic discovery and then --provider
or
first --provider and then automatic discovery
I would like to add this function, but unfortunately I am not able to do so.
Or at least add the http trustless gateway--provider http://trustless-gateway.link--provider http://ipfs.io into the default automatic content routing based discovery. 🙏 @rvagg@willscott
The text was updated successfully, but these errors were encountered:
Sometimes the automatic content routing based discovery finds no providers/candidates.
So I have to add manually additional --providers value which are not on DHT or cid.contact.
Unfortunately, this disables automatic content routing based discovery.
It would be very helpful if I could define via CLI when adding one or more
–providers value
that the that the automatic content routing based discovery remains activated.The definition of the discovery sequence would also be very helpful:
--provider
or
--provider
and then automatic discoveryI would like to add this function, but unfortunately I am not able to do so.
Or at least add the http trustless gateway
--provider http://trustless-gateway.link
--provider http://ipfs.io
into the default automatic content routing based discovery. 🙏 @rvagg @willscottThe text was updated successfully, but these errors were encountered: