meh.

No, that's not how it works. The only possible reason is different default options between the binary and the library.

I honestly don't know, someone should have to dig around the binary's source code to figure out what differing default options are there.

Does this actually make it work? `TessResultRenderer` is not a `STRING` anymore, and the Ruby side expects a `STRING`.

Would this also fix #1742?

Oh, got it, it's what happens when a file is missing in the migration directory.

What Range? Can you link to the MDN page please?

I sincerely don't like abuse of the protocol like this, it would be better to implement it as a protocol extension.

@prof7bit I think it's either protocol extensions for every command (which would easily become an infinite list, so it's not reallya good choice), or a single packet to handle all...

> We don't need son for the data. TorChat packet payload may be arbitrary > binary data and for simple things (like a ping) that can be expressed in >...

I wrote the [latency](https://github.com/meh/ruby-torchat/blob/master/doc/protocol/latency.md) protocol extension, already implemented in ruby-torchat. Don't think it will need anything else, any feedback?