Irakli Gozalishvili

@warpfork would love to see what you think about it

> @Gozala can you talk more about the use-cases you have in mind for this? Primary use case that came up is discussed here https://github.com/ucan-wg/ucan-ipld/issues/4 and also motivated me to...

> @Gozala : are you planning to take on this work? I'm not sure what taking this on would entail, but I'm happy to help where I can. I believe...

I would personally prefer not to introduce dependence on URLs and instead embrace IPLD native links instead, e.g syntax for the bringing defs from other schema may look like regular...

@RangerMauve I think it would be a great idea to also evaluate idea from [unison language](https://www.unison-lang.org/learn/the-big-idea/), which uses [hash based, as opposed to named, referencing](https://jaredforsyth.com/posts/whats-cool-about-unison/#Code-chunks-functions-values-are-stored-by-the-hash-of-their-contents-not-by-name) which in turn eliminates need...

Yeah sadly we also had not so great experience with skypack things working on one version and stopping in the other. In our case it was one of the dependencies...

Maybe this could be re-framed to make it possible to load this lib on observable (and other ESM native runtimes) ? I might also give this a go if I...

> The checking for capabilities needs to be configurable, and the wnfs capability logic should be supported by default by this library. I was going to suggest exactly that, but...

I also think that fact that there is no general way to compare capabilities might be a design flaw. While it makes system open ended it also makes it bit...

> I disagree about providing that much information on errors. It's not like that would be useful for error messages in apps to users with broken UCAN chains. It's more...