-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Download & upload IPNS records through API / CLI #10484
Comments
@cornwarecjp not sure how useful for your use case, but kubo/.github/workflows/gateway-conformance.yml Lines 77 to 83 in 3308185
Just to clarify my understanding of your request, we seem to already have APIs for both reading and writing:
What is missing? What are ergonomics you'd like to see?
Would a dedicated command |
@lidel Thanks for the response. I wouldn't have expected IPNS operations under From the documentation, it's not clear to me what BTW, on further searching, I also found A dedicated |
afaik
|
Checklist
Description
I would like to have API / RPC functions for downloading / uploading IPNS records. This should include both our own records and third-party records. The reason for this is that I have application-level knowledge of who might have these records and who might be interested in them, so exchanging records directly (whenever two parties are online simultaneously) is a fast and efficient shortcut for my application. Being able to also exchange them through the IPFS network is a nice extra, for redundancy / scalability.
When uploading an IPNS record to Kubo, it's important to know what happens if Kubo already knows a more recent record for that name. I'd say, by default, it should return an error and keep the more recent record. For my application, that behavior will do fine.
When uploading an IPNS record to Kubo, one might want to specify whether it should be pinned (as soon as IPNS pinning is implemented; this feature is already requested, e.g. in #1958 ). I'll add some pinning-specific thoughts to #1958.
The text was updated successfully, but these errors were encountered: