-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Consider defaulting to IPFS for metadata hash #5064
Comments
Do you have a suggestion for metadata configuration options in standard json? |
I thought about just switching, but the config option might be named |
Added a test file: QmdB5JktqW6LPioJXACMxPqLeB36LtZ4ZN8oE31EkiuAHt |
After some failures, we started another ipfs node on the same network, it automatically connected to the first node and got the file. It still was not on the gateway but when I checked 30 minutes later, it appeared on the gateway. So now I think the next test is to wait for some days and re-check if it is still on the gateway. |
Added another file which we also retrieved via the cloudflare gateway (to see whether its cache might have longer timeouts): QmXqNvVwR4hhNmwotFkHAosXnsxV8M7AdzxePvg5fXvYX8 |
The file that was also previously retrieved via cloudflare was available immediately (both on cloudflare and on the "official" gateway). The other file seems to be gone. |
File is still present. |
I guess we now have positive data towards IPFS? |
Looks like it... |
Still present. |
Will do the change in 0.6.0. |
Still present. |
Now that cloudflare added an ipfs proxy, we might be much better off defaulting to ipfs.
Any opinions?
The text was updated successfully, but these errors were encountered: