Irakli Gozalishvili
Irakli Gozalishvili
> I think @mikeal's remaining makes more sense than path in your `IPLDLinkEntry`, however. It needs little or no clarification. > Depends on the context IMO. If you think about...
> I prefer "remaining", as "path" to me is to ambiguous it's not clear to me if it's the path to the CID or the path to the value after...
I think “remaining” makes sence if you’re thinking about in terms of reaching a destination. But if you think of link to something, or a poiner then “remaining” starts to...
> One last thing to note, the `encode` interface should be optional. We have codecs that we need to read but will probably never need to write with this interface...
> `dag-json` is a “codec” that uses the `json` “format.” Wait is this a desired terminology or undesired ? I feel like this exactly the right terminology which I see...
> I went with `codec` for consistency, as the `multicodec` project already had their naming locked in and I wasn’t going to be able to change it, and our “codecs”...
I have wrote up proposal to introduce `MultihashVerifier` interface which could be used to verify hashes. I would suggest to make passing an instance in the reader mandatory and in...
Return value of util.serialize(dagNode.toJSON()) should produce equal value to `dagNode.serialize()`
For my specific use case it would be even better if `Data` and `Links` getters were just turned into regular properties. That would make it unnecessary to call toJSON at...
> Re: the capabilities. We should discuss (on the call) how to do this stuff without reimplementing libp2p. 😅 Is there reason to not collaborate on libp2p itself? Reading this...
> I think for the same reason it's healthy to have both KDE and Gnome, or Mozilla and Firefox, or Linux and FreeBSD, it's not wise to create a monoculture....