Prevents telnet options from getting set incorrectly.

TG_ECHO, or TG_LINEMODE for RLogin (the protocol specifies these values).

This fixes the GeoIP motherfuckedness.

super-strangeness with the previously unfucked matchuser().

The previous re-unfucking used the global query variable and would never
use the BBS users location.

char.

Thanks for the bug reports.

JPath.$$() now returns an array of JPath objects (instead of a single JPath object containing an array)

Fix a bug where someone's security level could be set <0.

(Can check console.terminal for this value at the top of logon.js, and launch ax25shell.js if so.)

If text/badwords.can exists, will mask those words before sending them to an AX.25 client from an rlogin tunnel.
(This could be moved into the AX25.Client object in kissAX25lib.js instead, at some later date.)

The beginnings of a command shell geared toward AX.25 clients, with ANSI, colour, and extended ASCII available if the client wants them.
Right now it's enough for reading (and, just barely, posting) messages and changing account settings.

To do:
Create a custom line-by-line message editor.
Cyan should provide an IRC client as well.
Censorship filter either here or in ax25tunnel.js.
Add all kinds of other exciting features.

(Will make it possible to map each of a user's 16 available SSIDs to a particular service later on, using eg. VA7RRX-0 for RLogin, VA7RRX-1 for QWK networking, etc.)

Gates between AX.25 unproto clients and the terminal server (rlogin).
Still a work in progress; new user account creation improvements forthcoming.
A command shell geared toward these clients will appear in the near future.  It works passably well with classic_shell.js for the time being.

Now supports all KISS commands, and multiport TNCs, buffered send and receive of packets for more gooder throughput.
Closer to a complete implementation of AX.25 2.2, with timers, command/response, poll/final handling now in place.
Various other improvements.

slightly improved JSDOC descriptions.
Updated JSDOC description of the 'js' object to be more general.

This is to deal with the fact that when you concatenate JS strings, the JS
engine simply notes that they are concatenated, but keeps all the original
strings around until something flattens them.  This code:

for(;;) {
	str += ascii(random(256));
	log(str.length);
}

Fails when str reaches about 256KiB then crashes with out of memory but
this code:

for(;;) {
	str += ascii(random(256));
	log(str.length);
}

Reaches a size of 4MB without stopping.

Any time you actually paw through the string, it gets flattened, but when
you do a bunch of concatenation, manually flattening can be a Good Thing.

Try to recv() Content-Length bytes when specified, and 1024 bytes at a
time when not.
Call js.gc() after each recv().

The gc() call fixes the "out of memory" error which occured on HTTP pages
over about 128KiB and makes reading web pages considerably faster.

the default IRC server/port and channel name.