TL;DR: Cloudflare-ipfs seem to be going to a premium model. Not sure how that would work with current model of public gateway, which is still available for now.
Today I discovered on https://cloudflare-ipfs.com/ page that IPFS and Ethereum gateway are now premium. There’s “free” version with 50GB/month traffic limit, as well as other plans.
There’s no mentions of /ipfs/ / /ipns/ URIs on the page anymore. I could not find any announces anywhere about changes in service model.
Right now my /ipfs/ links and my websites, which were registered using old panel available on cloudflare-ipfs.com website without any accounts or registration, still work. But for how long will that be?
They don’t advertise free version anywhere anymore. No /ipfs/ or /ipns/ links seen on the website. To me it looks like they’re switching from free-for-all public IPFS gateway model to a non-public one, where you need to register first, after which you’ll be able to reach only websites registered via Cloudflare panel, not any IPFS file.
Yep, that makes sense. The two sites I have running there are archives of websites accessed via ipns / dnslink.
Open gateways are…dangerous to run from a moderation perspective, and a risk for Cloudflare if they have to do moderation for all gateways (AFAIK there isn’t a per gateway moderation interface).
And I think Cloudflare, my team at Fission’s “beta” publishing platform, and Fleek are the only (?) three services that offer DNS <> IPFS automation?
Someone correct me if I’m wrong, I’m actively looking for more services like this.
This all-in-one will be a gateway. Typically people will add / update DNS entries through an external provider. Cloudflare is a common freemium DNS provider with a good api in order to update DNS entries programmatically.
So, step one, use provider host name, eg MYAPP.fly.app — or just an IP address for like Digital Ocean.
Step two, add example.com → configure to point at all-in-one, with wildcard DNS for subdomains.
Cloudron has DNS Automation built in and would take care of this too.
So example.com/ipfs/bafy1234 redirects to bafy1234.example.com
Step three, add DNSLink TXT entries that get mapped to the gateway. I think as we covered elsewhere, step three is a ways off. I can file that as an issue and a write up.
cloudflare-ipfs.com has started to redirect some of IPFS requests to ipfs.io with HTTP 302 redirect.
I guess this is the first step in sun-setting the gateway.
All traffic using the cloudflare-ipfs.com or cf-ipfs.com hostname(s) will continue to work without interruption and be redirected to ipfs.io or dweb.link until August 14th, 2024, at which time the Cloudflare hostnames will no longer connect to IPFS and all users must switch the hostname they use to ipfs.io or dweb.link to ensure no service interruption takes place.
