Chad Retz

Will do. I have mostly explained that it creates a class file and explained what the constructor and exports are which should be good enough. But I'll make it a...

I think the example in the README shows this

I haven't worked on this library much lately. As you've guessed, it appears the "cleanup on error" logic in `Listen` cannot safely handle closing its receiver before it has completed...

> Maybe I just didn't wait long enough? Did you make sure `Listen` returned before attempting to close? I think that is the key.

Onionbalance for v3 relies on a recent PR at https://github.com/torproject/tor/pull/1647 (discussion at https://gitlab.torproject.org/tpo/core/tor/-/issues/32709) which only applies to torrc-based onion services, not ephemeral ones via `ADD_ONION`. Mailing list discussion started at...

I'm afraid this still isn't enough to easily make a `net.Conn` out of a Windows socket. I would end up duplicating the FileConn efforts done in the Go repo issue...

@lu4p - Hi. This is a bit of work. I've played with it some, and you'll end up using syscalls to winsock APIs among other things. At first it seems...

Adding help wanted tag. Until the Go issues mentioned in the PR at #13 are done, this would be a manual effort w/ syscall.

Yeah, today I only support one `LocalPort`/`LocalListener` in the simplified listen API in the `tor` package (but we do support multiple remote ports). There's no specific reason not to accept...

if I revisit this, I think I may accept a port-mappings structure that will be mutually exclusive with the existing local/remote port pieces. This will give the most flexibility.