This has been a great discussion so far. Seems like there is strong (not unanimous) agreement on the current challenges, and general enthusiasm for hash equivalency and cleaner libraries/interfaces. I propose that we:
- Move profiles into IPIP process - Agree on a minimal set of profiles & names, plus process for canonicalizing. This may include working with kubo to update the name of
test-cid-v1. We could have this discussion here, and move to PR to specs repo when there’s a more concrete proposal. - Consider more minimal implementations - Start a new thread about leaner IPFS implementations with key functions: hash, hash --profile, verify, [others].
- review prior art by community: Debian / Rust Cid Npm · GitLab
- review prior art by community: GitHub - MarshalX/python-libipld: 🏎️ Fast Python library to work with IPLD: DAG-CBOR, CID, CAR, multibase
- incorporate ideas from thread & elsewhere, like: If i have a cbor decode of data with a cid, I get a 42 tag, and then some hex, typically. it would be great if something like cid.ipfs.tech could more easily massage that back into a sane cid, versus the current workflow of having to write a script each time i encounter a binary cid in the wild.
- Host some sessions at IPFS Bangkok in Nov to work on these in person, in parallel with async/online.