Also, can't tell, but does the webrtc client overcome this bug?<p><a href="https://tensorworks.com.au/blog/webrtc-stream-limits-investigation/#:~:text=Section%206.6%20of%20the%20spec,to%20safely%20avoid%20this%20problem" rel="nofollow noreferrer">https://tensorworks.com.au/blog/webrtc-stream-limits-investi...</a>.<p>Probably not. I have a theory that webrtc hasn't found it's footing because the native client doesn't appear to appropriately error out large messages.
Some documentation on how to use this would be great. I understand the core concepts of WASM, WebRTC, and DHT (not specifically Chord), but it's not obvious how to actually use this.