Alex Kirszenberg

@rlindsberg I've added you as collaborator.

This error happens because I didn't fix the version of `grunt-contrib-coffee` in [dependencies](https://github.com/Morhaus/dispatch-proxy/blob/b39f0999ca9ce1a2c59b63687e2b9a9112e8bfa8/package.json#L39), which means that between the last time I compiled the code and today, the CoffeeScript language has...

ES6 and CoffeeScript are two separate languages, so there is no other option than rewriting from scratch. However, translating from CoffeeScript to ES6 is fairly straightforward. When I built this...

If you're having trouble understanding something, don't hesitate to ask :) I'll review your PRs and let you know when you can do something better. I think the best thing...

Also, remember that running `node ./bin/dispatch.js` will use the code under `lib/`, so don't forget to make sure it's up to date by running `npm install` or `npm run watch`.

@rlindsberg Let me know if you need some help or pointers. I have some time as I'm on holidays for a week, and I've wanted to bring this repo up...

The SOCKS proxy works on HTTPS sites, although it won't dispatch requests with `Connection: Keep-Alive` to different network interfaces.

You can force `dispatch-proxy` to go through another proxy via Proxifier, by creating a rule for the `node` process.

The port most likely has nothing to do with the error. I take it `0.0.0.0` is a placeholder address, not the address you really are using? Otherwise, I encourage you...

What's the output of `dispatch list`? Have you tried using each connection separately with dispatch, to check if they work individually?