-
Notifications
You must be signed in to change notification settings - Fork 106
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
Allow for custom data transfer mechanisms #109
Comments
@MarcoPolo : is this a duplicate of #98 ? |
Yes, thanks. I didn't find that one. Closing in favor of the other one. |
@MarcoPolo This is now possible on the |
achingbrain
added a commit
that referenced
this issue
Jan 8, 2024
Remove deprecated interfaces for newer versions.
achingbrain
pushed a commit
that referenced
this issue
Jan 8, 2024
## [@helia/ipns-v2.0.3](https://github.com/ipfs/helia-ipns/compare/@helia/ipns-v2.0.2...@helia/ipns-v2.0.3) (2023-10-26) ### Bug Fixes * update libp2p interfaces ([#109](ipfs/helia-ipns#109)) ([514b6e1](ipfs/helia-ipns@514b6e1))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please correct me if I'm wrong, but it seems like bitswap is always activated if you provide a libp2p object to the helia constructor. I would like a way to either:
I would like this so I can plug in alternative data transfer mechanisms like using the HTTP gateway api.
The text was updated successfully, but these errors were encountered: