Irakli Gozalishvili

> * js-multiformats commit history is likely the place to find reasoning for the weird `typesVersions` usage, we've had to deal with multiple TS bugs and issues in there and...

> Some projects have a test/ts-use/ TS project in them, I'd love to see this rolled out further across the projects and expanded too to test more of the types...

> It seems like we're leaning toward not checking in types to the repo but only doing it on publish, I'm fine with this as long as (a) we're type...

> The biggest thing I'm going to miss with all of this is the ability to `require` from the Node.js REPL, currently I can easily `require('/path/to/js-dag-cbor/dist')` to get dag-cbor .....

> 1. You don’t want to entirely conceal the links. If you don’t provide the links in a un-encrypted way, you would have to share the key with any system...

> What about the keys needed to do actual decryption ? Never mind. In my head I was still thinking of two layers of encryption which is not what you're...

>> Instead, what you want to do is provide a list of links that exist in the encrypted block but without any other information about them (like the map key...

I made some progress on my encrypted data feeds that attempted to incorporate suggestions made here. There are few things I learned in the process that I would like to...

> @Gozala the double encryption here is so that the data is completely obscured to the public but a replicator can access the links that need to be replicated but...

Few more thoughts: - IPLD encodes `codec` info into CID, when Dag node points to it that presents enough info to a resolver as from the link it can figure...