Thanks, I have two more soon to come (these will be much smaller/slower).
Afaik eternum.io
needs to be www.eternum.io
. Just tried it without the āwwwā, and it didnāt work. (?)
Quick shell version. Note that sed
substitutes āeternumā for āwww.eternumā, which needs to be removed once the gateways list on Github has been updated.
<removed>
Removed: updated version below
I would recommend including that shell script in a PR in the repo posted above ^, Victor might oblige.
Iāve created a pull request: https://github.com/ipfs/public-gateway-checker/pull/9/commits/ef635b24ffc7970b98f00f18d182c2f3fc62c3cb
I hope to have a 100mbit dedicated public gateway setup in the next few weeks. Once that happens, I will reply with details.
Updated for pull request, but moved to the following repo due to size: https://github.com/JayBrown/Tools/tree/master/ipfg
CLI has been updated to v1.2.1: https://github.com/JayBrown/Tools/tree/master/ipfg
Now includes option -u | --upload | --cache
to cache an IPFS object from your local node or a remote node on a public gateway.
Iāve added a couple of URLs via pull request:
http://cloudflare-ipfs.com/
https://nuts.rtradetechnologies.com:6772/ipfs
https://nuts.rtradetechnologies.com:6772/ipns
Just got these online earlier this week, they will be refined as time goes on. Attempting to browse anything other than /ipfs/...
and /ipns/...
will redirect to google.
I used to use these gateways quite a bit, is there any reason they might be acting slow?
For context: Iām working on a machine learning algorithm that opens a random port, and then using localtunnel to make it a temporary public URL. Since Iām having trouble reinstalling localtunnel, I thought I might try rewriting the code to use IPFS instead.