Skip to content

feat: support bitswap over http #675

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.

Sign up for GitHub

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

Jump to bottom
Open
SgtPooki opened this issue Mar 22, 2024 · 2 comments
Open

feat: support bitswap over http #675

SgtPooki opened this issue Mar 22, 2024 · 2 comments
Labels
dif/medium Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked

Comments

@SgtPooki
Copy link
Member

see ipfs/service-worker-gateway#8

We need to move that code over here
@SgtPooki
Copy link
Member Author

SgtPooki commented Nov 7, 2024 •
edited
Loading

@MarcoPolo we chatted about this today in the Helia WG. We will likely add this as a block-broker in Helia. Do you have any extra information or updates we should know about?

Do backend nodes support this today if we were to add a block-broker now?

@SgtPooki SgtPooki transferred this issue from ipfs/helia-verified-fetch Nov 7, 2024
@MarcoPolo
Copy link

Nice! I think usage should be pretty straightforward, but you may snag on edges that haven't been sanded down yet.

Do backend nodes support this today if we were to add a block-broker now?

It's a bit of a chicken and egg problem right now. But I think it makes sense to start on the client side first.

@SgtPooki SgtPooki added P3 Low: Not priority right now dif/medium Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature status/ready Ready to be worked labels May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dif/medium Prior experience is likely helpful effort/days Estimated to take multiple days, but less than a week help wanted Seeking public contribution on this issue kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now status/ready Ready to be worked
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MarcoPolo @SgtPooki