any moment without notice" means that it won't sent an OPT ND.  Just in case,
handle a -1 offset as though NR mode is enabled when version is 1.1.

this session, SKIP files that already exist, and ACCEPT all others.

No longer try to append extra data packets to the end of the file to allow
files to grow in transit... the protocol is really not well suited to this
anyway.  Instead, truncate to the advertised length.

If the want_callback changes the file name, still ACK the correct file.

Escape filenames more consistantly.

filter unwanted properties" warnings by default.  This is more for when
you're worried that your object may be exitended... a rare situation in
Synchronet JavaScript.

Reset senteob when addFile() is called on a 1.1 session.

binkp/1.1 requires rescanning the outbound after every received file after
an M_EOB, and binkd at least will re-offer previously skipped files, we
can't implement this as a simple boolean.

The want_callback will need to track skipped files and whatnot to get this
effect.

This may now be completely good to go!

Add name_ver argument to the constructor and corresponding property so that
consumers of binkp.js can indicate their program name correctly.

Fix bugs in previous commit.
Use Date.toString() instead of system.timestr for TIME value.

callbacks.

Add an rx_callback property that is called whenever we successfully receive
a file.
Fix up skipfiles so it doesn't try sending until all the remotes files are
skipped.

A file is not successfully sent until we get an M_GOT from the remote.
That takes care of all the TODO items.

to the socket going away, and not having the latest js_socket.c.

session using MD5 with binkd.

session, then call the session() method rather than requiring any logic
in the user of the class.

FREQIT is now good to go.

a constructor it seems.

Start of a FREQIT config script.

it doesn't exist.

Not really tested yet.