-
Notifications
You must be signed in to change notification settings - Fork 3
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
Clarify scope #35
Comments
@achingbrain : before we move on from delegated routing work for the time being, I'd like to finish this. For example, I think showing how someone actually uses this with their Helia instance (i.e., they need to use https://github.com/libp2p/js-http-v1-content-routing ) is important. I also want to make it clear that if there are expansions to https://specs.ipfs.tech/routing/http-routing-v1/ that in order for it to be useful for Helia client users, code changes are need in this repo and https://github.com/libp2p/js-http-v1-content-routing |
@BigLep @achingbrain IIUC, instructions for using this are now at helia-delegated-routing-v1-http-api/packages/client/src/index.ts Lines 25 to 40 in 1db87c0
I don't believe we need libp2p/js-http-v1-content-routing anymore since #44 was merged. However, i think there are still some things that need addressed, because i'm having to patch this package in helia-http-gateway: ipfs/helia-http-gateway@ce971eb |
Closing as I think all items here are complete. |
Things that I think we should make clearer in the README:
The text was updated successfully, but these errors were encountered: