Readme file for Overdose 0.3.1-ALPHA

---0.3.1---
ymsg.[ch] are for Chat2, which is our new protocol. It uses YCHT-style HTTP 
cookie authentication with YMSG protocol for main communications. However,
the YMSG it uses is it's own version (like YCHT11 is not YCHT12 and so on)

I need a bit of help, though, cause the most recent implementation I have is in
Perl, and I can't read Perl for shit. Damn pack().

Yes, We are back in action.

---0.3---
The make system has ben almost completely rewritten. The parts that were already
modular were left intact (if it ain't broke, don't fix it.) Most of the old Makefile
was broken, so it was rewritten. wincross code is now in it's own Makefile.

The number of string functions provided by Overdose has increased. These are nice in
case you need to port to a weird system that ironically is missing a function (or two).

We currently have (almost) all the code needed to use YMSG. Anyone feel like helping me?

There is code in place for an ignore system, but it doesn't work.

The config file is now ~/.overdoserc

The ignore file is ~/.overdoseig, and is in the same format as the Zinc ignore file. If
the Zinc ignore file exists, Overdose will attempt to import the data. 

We need a function that will remove duplicate members from a array of strings, and sort 
the array alphabetically.

---NOTICE && 0.2.2 && 0.2.3---
Please skip ahead to near the bottom for the command list.

Nothing new for 0.2.2 and 0.2.3

---0.2.1---
I have added a /exec command that runs the passed command as if you typed it at the shell yourself! this means you can use ~, ;, and other shell doodads in your /exec commands. Please be aware that the largest amount of text sendable at once is 512 bytes.

---0.2---
Please note that this client uses YCHT, and that your favorite YMSG client may
connect while this one doesn't, that's because your regular one uses a 
different protocol and server entirely, and to say that mine's broken when 
it won't connect or login after being warned is a id-ten-t error on your
behalf. YCHT's servers are buggy, that's that's not my fault/problem.

I am finally documenting the fact there is a config file. It does not work, 
however. The file is ~/.overdose , and it's format is straightforward:

<server>
<room>
<user>

There is not special formatting, just everything listed above, in that order, as
plaintext.

There is a new command: /timestamp. It adds timestamps to the console text.

Overdose now works in Windows, yay!

The /target command dumps the build target to either the chatroom or the 
local console, depending on if you are in a chatroom, like /ver does.

---0.1.5---
Good news! Overdose no longer needs or uses glib! A portable vasprintf is 
included. This has been done since 0.1.4-ALPHA, but I accidentally saved that
version's README as '1'. It shall be renamed to 'README-0.1.4-ALPHA'

The /ver command's output will show up in color if you aren't in a chatroom.

The program's Process ID (PID) will be printed when the program starts.
---0.1.4---
A unsupported and broken 'xcurses' target was added. Due to the fixed-terminal
windows of xcurses (the X11-native version of PDCurses), resize_term is neither
available or of any use if it was. -DNORESIZE was added to the xcurses make 
target.

I hope to test Overdose on a uClinux system soon, even if it is just a 
normal x86 system running the uClinux kernel and/or uClibc. I started a thread
on the DSLinux forum about running Overdose on DSLinux, and if it works...
Thread URL: http://www.dslinux.org/index.php?showtopic=1324
---0.1.3---
More Winsock #ifdef __WIN32__ stuff was added. I will probably end up with
more #ifdefs then the world asks for.

The strsep() function is from a patch submitted to the glib mailing list years 
ago, and never made it into glib. Hopefully it puts the author at rest knowing 
his function isn't totally wasted.

The snprintf library is licensed under the Artistic License, check the file
LICENSE_snprintf.txt for more information.

--0.1.2---
At this time, /me is known to be broken. Please don't send me bug reports, I 
already know it's broke. Any patches to fix it would be appreciated.

A few of the regulars in Linux, FreeBSD, Solaris:1 make accusations that 
Overdose uses stolen Gyach code. These claims are unsubstantiated, as gyach is a 
YMSG client that uses GTK+-2.0, and Overdose is a YCHT client using any curses
implementation supporting resize_term (hacks are available for non-conforming
implemetations).

---0.1.1---
Also, the /ver command has been changed to include the machine type, OS, and 
version of the machine that built it. This is *NOT* nessessrarly your current
running machine, just the machine that built it. It could have been 
cross-compiled from a SPARC running Solaris 9, in which case it would read:
"I am using Overdose 0.1.3-ALPHA, built on a sparc64 running SunOS 5.9"
This is not a BUG, and if you think it is so, you're retarded.

---LIST OF RUNTIME COMMANDS---
COMMANDS:

/server		-- select YCHT server. If one is not specified with the 
		   command, you will be prompted for one. Just push ENTER
		   without entering anything to select the default server.
/login		-- login. If an username is not specified, you will be prompted
		   for one.
/me		-- Emotes. This feature is currently broken.
/quit		-- Quits overdose. /q also works.
/ver		-- Spams your chat client version in the room.
/connect	-- Connect to the server
/disconnect	-- Closes connection
/login		-- Logs into server. You can put your username after it.
/join		-- Join a room. Unless one is specified, you will be prompted. 
		   The default room is "Linux, FreeBSD, Solaris:1".
/timestamp	-- Toggles timestamps. These are off per default. Alias: /ts
/logout		-- Logs you out without disconnecting. The socket is held open.
/exec		-- Runs shell command, output sent to chatroom.

--- NOTICE ---
There are several command-line options, however, the system that understands 
them for Overdose is somewhat broken.

A prebuilt binary for Linux is also included. It was compiled with a gcc 
patched for stack-smashing protection. If your gcc is also patched for SSP,
you can uncomment the second set of CFLAGS in the Makefile. 
