Bumblefudge

@rvagg @vmx Sorry for the late appearance, this crossed my inbox last week but I was at TPAC on a borrowed laptop and couldn't get here in time. > My...

oh totally the sigil is yours! sorry it didn't land sooner.

Are you recommending that dave's crate be refactored into TWO crates, the parser and the supported codecs, so that projects could just fork and subset the latter when they wanted...

Ah, ok, gotcha. I think the context of this is packaging a general-purpose libp2p library for use-cases beyond IPFS/IPLD, so I presumed it's already a crate that would be maintained...

Late to the party here, but I would add that `base64url`/`u` (not `base64`/`m`) is foundational in the OIDC world, so any multiformats system that wanted to be able to encode...

@hmalik88 does the new cross-link look ok? technically i need a 2nd not-me reviewer :D

LGTM with minor edits, which i left on [your fork](https://github.com/TowoLabs/namespaces/pull/3). Are there already public and open source implementations of this that you can link to from the # References section?...

Update: since [caips#160](https://github.com/ChainAgnostic/CAIPs/pull/160), `-` (or rather, `---`) could now be a valid CAIP-2. This might be a little too much "wildcard" for existing CAIP implementations, but I am generally favorable...

in terms of wildcards and non-chain IDs in the chainId segment of CAIP-10, there is now precedent in another namespace that may be relevant to this PR: https://github.com/ChainAgnostic/namespaces/pull/107

A/B/C refers to: