-
Notifications
You must be signed in to change notification settings - Fork 29
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
docs: clarify subdomain CID normalization #164
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great clarifications. Gave a few optional suggestions in review comments.
Added a couple of notes. I'm not too clear on the purpose of this doc. Is this a guide instructing the reader to do something? Or are we saying these things happen in this feature? |
Co-authored-by: Johnny <9611008+johnnymatthews@users.noreply.github.com>
I've applied suggestions from reviews. @johnnymatthews – mind taking a final look? |
The rest looks solid to me! Just that one tiny change 😄 |
Co-authored-by: Johnny <9611008+johnnymatthews@users.noreply.github.com>
This PR adds more detail into "best practices" when implementing
ipfs://
URI backed by a subdomain gateway.Namely, opening a path with CID as-is, to take advantage of DNS normalization built into go-ipfs 0.5+
This should help with native URIs in Brave (brave/brave-browser#10220) when embedded go-ipfs is turned off and other collabs.