Jer Miller

The raw packet format has two parts, json and binary, so (reliable) channels can be created between any two hashnames that contain either or both... the binary is just raw...

I added bare key support in [v2](https://github.com/quartzjer/js0n/tree/v2) but didn't go so far as supporting comments, mostly because I wanted to support `// foo` newline based and that's more complicated still...

Both Windows Defender and Malwarebytes are flagging 1.9 and 1.10 as [Wacatac.B!ml](https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Trojan%3AWin32%2FWacatac.B!ml&threatid=2147735505) or [Neshta.Virus.FileInfector.DDS](https://www.malwarebytes.com/blog/detections/neshta-virus-fileinfector-dds). 1.8 seems fine.

There's some working test cases now to validate the transactions on testnet w/ 0.10.

I did a small [webrtc-peer](https://github.com/quartzjer/webrtc-peer) module to try and create a minimal reusable component that was distinct from larger efforts like peerjs, had it working but not in production yet...

I agree with [this comment](https://github.com/w3c-ccg/did-method-web/pull/50#pullrequestreview-834762306) by @tplooker and would 👎 dropping `.well-known/`. The did:web ID is machine-translated into a HTTPS URI for automated GETs, it's not intended to be a...