Skip to content
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

Replace ipfs.io with dweb.link #939

Open
4 tasks
lidel opened this issue Oct 30, 2020 · 0 comments
Open
4 tasks

Replace ipfs.io with dweb.link #939

lidel opened this issue Oct 30, 2020 · 0 comments
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

Comments

@lidel
Copy link
Member

lidel commented Oct 30, 2020

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:

Ref https://docs.ipfs.io/how-to/address-ipfs-on-web/

@lidel lidel added 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/ready Ready to be worked area/cidv1b32 Moving to CIDv1/Base32 by default exp/wizard Extensive knowledge (implications, ramifications) required effort/days Estimated to take multiple days, but less than a week labels Oct 30, 2020
@lidel lidel added this to the v2.16 milestone Oct 30, 2020
@jessicaschilling jessicaschilling added status/blocked/upstream-bug Blocked by upstream bugs and removed status/ready Ready to be worked labels Nov 2, 2020
@lidel lidel modified the milestones: v2.16, v2.17 Nov 18, 2020
@lidel lidel modified the milestones: v2.17, v2.18 Jan 11, 2021
@lidel lidel modified the milestones: v2.18, v2.21 Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
No open projects
Status: Needs Grooming
Development

No branches or pull requests

2 participants