-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop relying exclusively on Infura for IPFS #27
Comments
The current state
Download:
We should, in both cases use the user's locale IPFS node, but fallback to the Infura services. The state that we want
Download:
|
@cedricwaxwing: we need UI for letting the user specify an IPFS URL. How it currently works: What we need: For me, it would make sense if this was an option in the "address dropdown menu", like "Update Pinning Service", we could add "Update IPFS Node". The pop-up needs to explain that if no URL is specified it first tries to connect to a locale IPFS node at the default endpoint ( |
@manboy-eth I've taken a stab here. Let me know if this works or needs updating: Modal popup for Updating IPFS Node: And the updated dropdown (ignore the other changes, as those can be captured in #183 ): |
@manboy-eth About the download process, I think, for now, we're going to use |
We should check if there is a local provider available, if not, we can check if Infura is accessible, if not, we spin up a js-ipfs node.
Check this link for hardcoded
ipfs.infura.io
URLs: https://github.com/gnosis/tabula/search?q=%22ipfs.infura.io%22We do not want Tablua to be easy to censor ;)
The text was updated successfully, but these errors were encountered: