Kevin Jones

> I wondered if it might be (differently/also) useful to give it an initial buffer... not to say "start with these contents", but that for small or repetitive tasks to...

A completely separate idea would be to support one shot encoding for non-constructed items. ```csharp Span buff = stackalloc byte[256]; int written = AsnWriter.EncodeObjectIdentifier("1.2.3.4", buff); ```

I guess you could even do constructed items with `ReadOnlyMemory`: ```csharp byte[] oid1 = ArrayPool.Shared.Rent(512); byte[] oid2 = ArrayPool.Shared.Rent(512); byte[] seq = ArrayPool.Shared.Rent(512); int written1 = AsnWriter.EncodeObjectIdentifier("1.2.3.4", oid1); int written2...

> In that doodle there the BIT STRING and OCTET STRING types were the only ones that needed to know the encoding rules (because of CER). Well, I think character...

Another report of this via twitter from @ericlaw1979: https://twitter.com/ericlaw/status/1555303074054524932

>I would say, from my perspective, that we should use these two streams as they've been designed, that is: >* Operational output goes to STDOUT >* Errors and similar go...

This seems like a good idea. The idea being that we could flag certain errors as likely to lead to removal and adjust the UI accordingly, correct? While I tinker...

I can help, I have experience with TypeScript. What I am not sure on is how to integrate compilation in to your pipeline. 1. Do .js files as a result...

Ok. I can take a shot at this. I would propose a few PRs, or at least two. The first would be to just change the file extensions from .js...

I see: https://github.com/github/smimesign/blob/e650daf6eaadf85c763fa06dcfb0e4d794d293dc/ietf-cms/protocol/protocol.go#L755-L766 Since we're passing in something that is not an `ecdsa.PublicKey`, none of the `if` checks match and it defaults to SHA256. I think this change looks good,...