3f777ce5e2
If a valid escape (\n, \s, or \\) is found, increment the pointer marking the start of the next search so we don't start looking at the escaped character. The old behaviour was a problem for messages containing slashes -- the escaped slash would be looked at in the next pass and so the following character would be treated as an escape, causing the message to be dropped for having "an invalid ADC escape".
Welcome and thanks for downloading uHub, a high performance ADC p2p hub. For the official documentation, bugs and other information, please visit: http://www.uhub.org/ For a list of compatible ADC clients, see: http://en.wikipedia.org/wiki/Advanced_Direct_Connect#Client_software