-
Notifications
You must be signed in to change notification settings - Fork 17
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
Discovery of providers with delegated-ipfs.dev #489
Comments
I guess this is because the cid.contact endpoint isn't running cassette to query the DHT currently, right @masih ? Agree that these two endpoints should ideally be unified. Lassie currently uses the IPNI query endpoint, which came out before the IPFS delegated routing interface, and has a couple small differences in semantics that mean you can't 'just switch'. |
In terms of root cause this is due to the fact that delegated routing provide functionality is built around the way DHT provide works. IPNI is built for mass publication, and advertising the diff of what is no longer provided, instead of periodic one cid at a time publishing of CIDs onto the DHT. This fundamental difference makes it difficult to implement the backing for delegated routing provide in IPNI. A while back (2 years ago?) i proposed the notion of ephemeral advertisements for IPNI which would have been equivalent to the way DHT provide works where a content provider would need to periodically re-advertise content. That idea has not been implemented. |
About DHT lookup fallback: Cascade is not currently running on cid.contact. Operationally speaking it is expensive to run. If there is sufficient demand we can reconsider? |
If the DHT cannot be integrated into cid.contact, it would be nice if I could configure the delegated-ipfs.dev endpoint for the provider search in Lassie: |
Discovery of providers
For many CIDs that I want to fetch, no providers are found because they are not announced on ipni-endpoint
cid.contact
but on the delegated routing endpointdelegated-ipfs.dev
.It would be really helpful if the provider discovery would use the delegated routing endpoint
https://delegated-ipfs.dev/routing/v1/providers//routing/v1/providers/{cid}
How can I set up this endpoint for provider discovery in Lassie fetch?
https://specs.ipfs.tech/routing/http-routing-v1/#get-routing-v1-providers-cid
The text was updated successfully, but these errors were encountered: