David Konsumer

Another idea, instead of releases, is using [nightly.link](https://nightly.link/) to link to build-assets. I could merge the 2 ideas together, so you get bleeding-edge builds, but can also do tagged releases.

I merged the other PR here, so I can keep working on stuff.

Reading [here](https://emscripten.org/docs/porting/networking.html#emulated-posix-tcp-sockets-over-websockets) it seems like I can use similar to websockify and it might work fine, but I'd prefer to not have to setup & maintain a proxy, somewhere, if...

Sorry for the noise. I can add `Module[‘websocket’][‘url’]` in the browser, and it will use that instead, so I just need 2 ports, one for real sockets, and one for...

I got it requesting my other port, as the docs say, but I will need to play with the websocket server part, I think, as I couldn't get that working.

> To target WebSockets specifically, I really ought to link them at compilation time: I totally agree. I would way prefer real websockets in both, instead of cramming regular sockets...

I started work [over here](https://github.com/konsumer/lovejs-networking) and got the UDP local all setup and everything scaffolded for the rest. It goes kinda slow, and I still need to work out UDP...

Should we reopen this issue? I guess it's not really resolved, and then we can track progress & ideas on networking stuff better.

Also, I am seeing errors I didn't see before, when using [makelove](https://pypi.org/project/makelove/). I'm not sure what the difference is, but before I was just getting websocket errros, now I get...

Looks like maybe [Atomics.wake was renamed](https://www.chromestatus.com/feature/6228189936353280) Nov 2020.  In the outputted html, I did this: ```js Atomics.wake = Atomics.notify ``` Which got me further, but still...