Replace ipfs.io with dweb.link #939
Labels
area/cidv1b32
Moving to CIDv1/Base32 by default
effort/days
Estimated to take multiple days, but less than a week
exp/wizard
Extensive knowledge (implications, ramifications) required
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
P1
High: Likely tackled by core team if no one steps up
status/blocked/upstream-bug
Blocked by upstream bugs
Milestone
I believe we are at a stage where we should always use
dweb.link
on the web.Due to historical reasons we have separate settings for "default public gateway" and "default public subdomain gateway". Those should be merged and
dweb.link
should be the default gateway for use in browsers.This means:
ipfs.io
withdweb.link
as the default public gatewayhttp://dweb.link/ipfs/*
instead of subdomain version (to leverage future-proof CID fixups in go-ipfs)Ref https://docs.ipfs.io/how-to/address-ipfs-on-web/
The text was updated successfully, but these errors were encountered: