Alex Potsides

DCUtR for js-libp2p is in progress here: https://github.com/libp2p/js-libp2p/pull/1928

I've been doing a bit of investigation, what I've found is: 1. Browser connections are unstable - This causes remotes to drop connections, including relay connections 1. This can cause...

> Browser connections are unstable > This causes remotes to drop connections, including relay connections In recent releases this is much improved:

I can't run this repro case, even from @SgtPooki's update above. After running `npm ci`, I get: ```console % npm run success > success > node case-success.mjs [middle info URL]...

I think what's happening here is that the publishing node is missing a provide step. I've put a demo repo together here that shows how retrieval in browsers works and...

Historically supported versions have been covered by the [IPFS contributing doc](https://github.com/ipfs/community/blob/master/CONTRIBUTING_JS.md#supported-versions) though to be fair, it's looking a bit out of date - still talks about webpack and ES2015 doesn't...

Sorry for the delay in getting to this, it does look like very strange behaviour. Looking through the `p-event` code, it adds the event listeners synchronously as you've found. Any...

4-8ms is an eternity for synchronous code so there's definitely something weird happening. I've tried to create a repro from your description here https://github.com/achingbrain/libp2p-webrtc-ping I'm having problems replicating with Chrome*,...

I've tried running https://github.com/achingbrain/libp2p-webrtc-ping on two MacOS machines on a LAN with both running Chrome but I still can't replicate the issue. If the problem is that the `open` event...

Awesome, thanks - I'll check back here in a couple of weeks.