Skip to content
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

support downloading dag-cbor nodes as CAR files #1962

Open
yusefnapora opened this issue Jan 25, 2022 · 4 comments
Open

support downloading dag-cbor nodes as CAR files #1962

yusefnapora opened this issue Jan 25, 2022 · 4 comments
Labels
effort/days Estimated to take multiple days, but less than a week kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/blocked Unable to be worked further until needs are met

Comments

@yusefnapora
Copy link

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:

Screen Shot 2022-01-25 at 4 14 06 PM

And pasting it into the main search box on the desktop interface gives me

Screen Shot 2022-01-25 at 3 59 12 PM

If I click through to the IPLD explorer I can see the json representation and links to the NFT assets:

Screen Shot 2022-01-25 at 4 18 04 PM

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 export and save a .CAR file.

@yusefnapora yusefnapora added the need/triage Needs initial labeling and prioritization label Jan 25, 2022
@welcome
Copy link

welcome bot commented Jan 25, 2022

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@yusefnapora
Copy link
Author

cc @dchoi27 - this is what I was mentioning earlier about NFT backups with IPFS Desktop.

@lidel
Copy link
Member

lidel commented Feb 25, 2022

We have wip PRs in ipfs-webui

afaik it is blocked by the need to update to the latest ipfs-http-client (ipfs/ipfs-webui#1840)

@lidel lidel added kind/enhancement A net-new feature or improvement to an existing feature status/blocked Unable to be worked further until needs are met effort/days Estimated to take multiple days, but less than a week P1 High: Likely tackled by core team if no one steps up and removed need/triage Needs initial labeling and prioritization labels Feb 25, 2022
@lidel
Copy link
Member

lidel commented Mar 4, 2022

Related Gateway feature – /ipfs/{cid}?format=car – is being implemented in ipfs/kubo#8758

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/days Estimated to take multiple days, but less than a week kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/blocked Unable to be worked further until needs are met
Projects
No open projects
Status: Needs Grooming
Development

No branches or pull requests

2 participants