-
Notifications
You must be signed in to change notification settings - Fork 9
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
ux: add configuration toggle for delegated routing #288
Comments
@lidel I don't know if that fix is quite enough. If the delegated routing endpoints are being used for IPNS resolution (as opposed to using the trustless gateway endpoints) then we still need them around even if not doing direct retrievals. We could at the Helia level not turn on the content or peer routing systems though (or potentially use the trustless gateways for IPNS fetch). |
Yes, the idea here is to have "quality of life" toggle that disables all delegated routing, and only relies on trustless gateways. You can still do IPNS via trustless gateways alone, but if verified-fetch does not leverage it yet, we can simply error on IPNS errors, informing user they need to enable delegated routing. |
This seems like a duplicate of #267.
That's right. Currently, Helia is built in a way that accepts 3 kinds of routers (libp2p, delegatedHTTPRouting, and httpGatewayRouting) and by default includes both I've opened ipfs/helia#558 to address this gap in Helia. |
Descoping from Camp milestone due to impact on DNSLink (see #303 (review)). |
Do we still want to do this? I think the only action item here would be to disable delegated routing if direct retrieval is not enabled and trustless gateways are enabled. |
Current state
service-worker-gateway
sends a lot of requests tohttps://delegated-routing.dev
but (afaik) we don't have direct retrieval yet, so there is no benefit from itProposed UX fix
The text was updated successfully, but these errors were encountered: