Poga Po
@mafintosh I tried with 6.5.0 and 6.6.0. both have the same result.
I tried to find the root cause of the issue. Looks like the issue is in hypercore. I encountered some TypeError in hypercore's test so I'm current stuck there. Just...
Just tried the same code on `hyperdrive` v10. It still leaks listeners. ``` (node:94165) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ready listeners added. Use emitter.setMaxListeners() to increase limit ```...
IIUC currently there's no way to detach these new listeners after creating a diff stream. Hence I was thinking that it's a leak. I agree that calling it a leak...
I've tried on v9 and v10 and can reproduce the warning on both versions.
There are total 6 six event listeners leaked whenever we create a new checkout. Their corresponding events are: * append * error * extension * peer-add * peer-remove * ready...
Yeah, not registering these listeners on checkouts definitely make more sense. One limitation I can think of it is that `error` events will only triggered on the base archive. If...
I agree. We can definitely use better word choice here.
For PoC, we can simply encrypt the message for each participant in the private channel.
The simplest way to do this might be with [postToTopic](https://github.com/ailabstw/pttai-next/blob/master/frontend/src/Chat.js#L117) in the frontend. We can post a new message to the topic with `type = 'blob'` and `value = base64(blob)`....