A problem I've found with testing Twilio using Ngrok is the latency; occasionally connections will get closed by Twilio by timing out before they even hit my machine.
One of the core features of this release is improved latency, but if latency was ever bad enough to cause Twilio to time out, I consider that a critical issue. Please report it to me if you ever encounter anything like that in the future.
Great concept, thanks for sharing. This is a valid alternative to getting a cloud machine (e.g. EC2) and providing a reverse proxy from your localhost to an open port on the cloud machine.
Haven't tried ngrok yet, but maybe someone can tell me how it's different from creating an ssh tunnel (in a case when I do have a server/vps with public ip running sshd) ?
Stoked for the new features Alan - thanks!