-
Notifications
You must be signed in to change notification settings - Fork 905
support downloading dag-cbor nodes as CAR files #1962
Copy link
Copy link
Open
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/beginnerCan be confidently tackled by newcomersCan be confidently tackled by newcomershelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing feature
Metadata
Metadata
Assignees
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/beginnerCan be confidently tackled by newcomersCan be confidently tackled by newcomershelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing feature
I'm writing up some docs for nft.storage about how to make a local copy of your NFTs that could potentially be re-provided to the network (as a hedge against link rot, basically).
I was hoping to use IPFS Desktop for the examples, but it doesn't seem to like the dag-cbor nodes that nft.storage uses as its top-level "container" node.
When I try using the menu bar's "Download" command, I get this:
And pasting it into the main search box on the desktop interface gives me
If I click through to the IPLD explorer I can see the json representation and links to the NFT assets:
But sadly I'm not able to download or pin the entire thing, which is what I was hoping to do.
Solution wise, it seems like what I really want is broader support for dag-cbor in Desktop / web ui, but that sounds like a big nest of features and potential features that will take planning and so on 😄.
I think a good short term solution would be to have a "Download as CAR" option on the "This is not a file or directory" screen in addition to the link to IPLD explorer. Clicking the 🚗 button could call out to
ipfs dag exportand save a .CAR file.