-
Notifications
You must be signed in to change notification settings - Fork 25
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/wizardExtensive knowledge (implications, ramifications) requiredExtensive knowledge (implications, ramifications) requiredkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)topic/design-visualVisual design ONLY, not part of a larger UX effortVisual design ONLY, not part of a larger UX effort
Description
Explorer should show mtime
and mode
when present in dag-pb
, to make it easy to spot difference in optional metadata.
Right now two CIDs can have the same files but different mtime
/mode
and Explorer does not show any hint what is different between them. We need to decide how to present those additional (optional/implicit) attributes.
Ref.
- The IPLD Explorer UI lives in WebUI's explore tab and as a standalone website at: https://explore.ipld.io/#/explore/QmdmQXB2mzChmMeKY47C43LxUdg1NDJ5MWcKMKxDu7RgQm/
- unixfs1.5 specs: docs: adds spec sections for mode and mtime metadata (Unixfs v1.5) specs#226
- so far
add
withmtime
andmode
is only supported by js-ipfs: feat: support UnixFSv1.5 metadata js-ipfs#2621 - go-ipfs has an open bounty: [BOUNTY] Implement UnixFSv1.5 in go-ipfs kubo#6920
- so far
- An example of UX problem that we want to solve: https://discuss.ipfs.io/t/why-has-same-sub-cids-but-not-same-root-cid/8810/6?u=lidel
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/wizardExtensive knowledge (implications, ramifications) requiredExtensive knowledge (implications, ramifications) requiredkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)topic/design-visualVisual design ONLY, not part of a larger UX effortVisual design ONLY, not part of a larger UX effort