📄 readme.txt
字号:
off.html
The HTML page displayed when the chat room is offline.
Remember to run "./off" to refresh your index page and actually
turn chat off.
chat-top.html
Change this HTML to change the top of a non-frames mode chat session.
Be careful! Remember that this is only the TOP of the actual chat
page! (If you specify a "<BODY>" tag here, it will define the entire
page in a non-frames mode chat session.)
chat-bottom.html
Same as above, but for the bottom of the chat page.
(Do NOT specify a "<HTML>", "<HEAD>", "<TITLE>" or "<BODY>" tag here!!)
ad.html
Change this HTML to change the top frame of a frames mode chat session.
This spot is similar to "chat-top.html" for a non-frames session.
If you'd like this frame to reload, remove the "!" comment character
from the <meta> tag at the top. It would only be useful to reload it
if you have an SSI-based banner rotation program (like specifiable
in the "AD_CMD" define in "defines.h"). (If you specify a "<BODY>"
tag here, it will define only the top frame of a frames mode chat
session.)
chat-post-top.html
This is the top of the middle frame (the chat control panel) of a frames
mode chat session. DO NOT PUT EXTRA VISIBLE TEXT IN HERE! This
is mainly meant to let you set the colors using the "<BODY>" tag.
This file will probably go away in the next release.
chat-watch-top.html
This is the top of the bottom frame (the chat messages) of a frames
mode chat session. This is mainly meant to let you set the colors using
the "<BODY>" tag, but if you'd really like to (it is NOT RECOMMENDED)
you can put some text here too. Note that this fill will probably
go away in the next release.
leave.html
This is the HTML page displayed by "leave.cgi" when someone leaves.
Put links back to your website here, and, if you'd like, a form
(linked to a form-to-mail program) asking the person how their
chat was. (You should place "<HTML>", "<HEAD>", "<TITLE>" and
"<BODY>" tags in here, as the distribution file has.)
who-top.html and who-bottom.html
These are the top and bottom of the "Who's Here?" page ("who.cgi").
"who-top.html" should contain "<HTML>", "<HEAD>", "<TITLE>" and
"<BODY>" tags. "who-bottom.html" SHOULD NOT, but it SHOULD contain
"</BODY>" and "</HTML>" tags. See the distribution files.)
chat-left.html
This is the left column of a chat session. Make sure to keep it
horizontally thin, so that the actual chat messages on the right have
enough room. Note that you should, unfortunately, ALSO keep it
vertically short, so that people with browsers incapable of supporting
tables don't have to scroll up and down a lot to get to the control
panel and messages. (Do NOT place "<HTML>", "<HEAD>", "<TITLE>" or
"<BODY>" tags here! This is just part of an HTML table!)
robot.dat
This is a text file containing any number of 3-line entries.
* The first line is a word or phrase for the Chat Robot to recognize.
* The second line (no matter how long, it must not have any
End-Of-Line / Line Feed characters in it!) is the Chat Robot's
response to the word or phrase.
* The third line is a blank line, included for readability.
The second line may contain a "~" (tilde) character. This character
will be replaced with the username of the person the robot is
responding to.
For example, if robot.dat contained:
alone
You're not alone, ~! I'm here!
bye
Goodbye, ~...
If "John" were to send the message "aww man, I'm all alone!", the
Chat Robot would respond immediately with the message
"You're not alone, John! I'm here!".
And if "jane123" were to send th message "ok, bye everybody!", the
Chat Robot would respond immediately with the message
"Goodbye, jane123...".
swear.dat
This file contains a list of swearwords, one word per line.
Any attempt to send a message containing one of these words will
cause a response (in the Chat Control Panel) saying "NO SWEARING!"
and the message will NOT be sent.
Asterisk characters ("*") can be placed one either side of words
that may be plural or otherwise embedded in another word.
Words without asterisks must be single words to count as a swear word.
(Note: Sorry, this is currently still a bit buggy!)
For example, if the file "swear.dat" contained the lines:
ouch
*man*
Then the following words would count as swear words:
ouch
man
human
manly
mantle
But the word "slouch" and "ouchie" would NOT be sene as swear words.
If you'd like my chat room's list of swear words, please e-mail me
and I'll send them to you. kendrick@zippy.sonoma.edu
convert.dat
Similar to "robot.dat", this file contains 3-line entries of
recognized ASCII combinations, a graphics filename (and it's width),
and a blank line.
Any time someone uses a recognized ASCII combination, it is replaced
with a corresponding inline image. Images must be 16 pixels high
(this was chosen because the typical screen font used in browsers
is about 16 pixels high, and the ASCII faces recognized by the software
are 16 pixels high.) Images can be any width. 16 pixels wide
is recommended for icons and faces. Support for any size is allowed
since you may wish to convert words to graphics containing words.
(For example, the word "*gone*", which many chat room users seem to
use when they're sending their last message before leaving, can
be replaced with a graphic of the word "GONE" swooshing away.)
Note that the ASCII combinations recognized must contain characters
normally represented by the chat room. For example, if you wanted to
replace the common phrase "<yawn>" with an ASCII face of someone yawning,
you must write it as "<yawn>" because (so that the chat room
suppresses HTML) the "<" and ">" characters are converted into their
HTML representation. The only other character you may need is "&"
(ampersand), which is "&".
The graphics referenced in "convert.dat" must be stored in the "convert/"
directory of your chat room. (This directory may be elsewhere. See the
"PREPEND" #define in the installation section.)
Here's an example of a "convert.dat" file:
<yawn>
yawn.gif 16
@--`--
rose.gif 64
In these cases, if anyone were to type "<yawn>" in a message, it would
be replaced with the 16x16 graphic "yawn.gif" found in the "convert/"
directory. If anyone were to type out an ASCII rose: "@--`--", it
would be replaced with the 64x16 graphics "rose.gif", also found in
the "convert/" directory.
access.dat
See the section "Registered Users", below, for how to edit this file.
== REGISTERED USERS ==
To create registered users (users which need passwords to get in,
therefore one can be SURE that they are really who they say they are),
you must, in this version, edit the file "access.dat" (or whatever
you chose to name it; see the "ACCESS_FILE" define in "defines.h"):
This file is a text file that contains 5-line entries:
* Username (including dashes ("-") wherever spaces would be)
* Password (WARNING: THIS IS NOT ENCRYPTED!)
* Access level.
normal - normal user
systop - sysop user, able to run sysop commands
god - sysop user, able to run sysop commands and see all whispered messages
* URL (including "http://" or "mailto:".) Their username will appear as
a link to this address, unless it is the word "none".
* Blank line (for readability)
For example:
John-Smith
jsZ465$
normal
mailto:js@aol.com
JaneD
carrot4
sysop
mailto:jdoe@system.net
When a user tries to enter using a username listed in this file, they will
be immediately prompted for their password. To actually enter chat with
this username, they must provide the correct password. This means that
other users can't come in as imposters.
If you have set "MUST_BE_REGISTERED" in "defines.h", all users attempting
to enter chat must be listed in this file or they can't come in...
As a "sysop" or a "god" user, you have access to the following commands
while in chat:
TOPIC - Set the current chat topic. ie, "TOPIC 49ers Rule"
You can also set the topic when you run the "./on" script.
(ie, "./on 49ers Rule")
BAN - Ban a particular username or IP address from the chat room.
ie, "BAN Stupid-User" or "BAN 128.0.0.1"
To ban a block of IPs, enter a partial IP address, ie:
"BAN 128.0.0.". You can also ban users without being inside
chat. Edit the file "banned.dat" and add the banner username
or IP address to the file (each entry should be on a separate
line).
BE CAREFUL! Some services (like AOL and WebTV) use "proxies"
which are one or more servers that ALL users use indirectly.
If you ban one WebTV user by banning the domain (using 3 digits
as explained above), you will ban ALL WebTV USERS!!!
As a "god" user, you have "sysop" priveleges, AND you can read all
whispered messages. (This is useful to keep an eye out on harrassing
users on your chat room.)
Note: There is currently no way to edit the "banned.dat" file via the
web. This will come in a later version. For now, you must edit this
file in a text editor, as you would any of the files described in the
installation section.
== PHOTOS ==
To give a user a photo, simply make a 40x40 GIF graphic of them
and save it in the "photos/" directory. The filename must be
EXACTLY their username, replacing dashes ("-") (or spaces (" "))
with underscores ("_"). (Note, if you used the "PREPEND" #define,
the "photos/" directory must be at that location.)
The user "John Smith" (who shows up in the chat room as "John-Smith")
would have a photo graphic named "John_Smith.gif" stored in the
"photos/" directory.
Note that people's photos only appear on their MOST RECENT message,
to keep the room from getting cluttered.
If you'd like graphics to appear when people join, leave or are idle,
or would like to give the "Chat Robot" user a photo, create 40x40 GIFs
named:
JOIN.gif
LEAVE.gif
IDLE.gif
Chat_Robot.gif
respectively, and place them in the "photos/" directory.
== SERVER SIDE INCLUDES ==
A pair of Server Side Includes ("SSI's") are distributed with Free Chat.
One was specifically made for Free Chat ("inchat") and the other is
a general SSI created long before Free Chat ("random").
Note: For more SSI's and SSI information, see New Breed Software's SSI page:
http://zippy.sonoma.edu/kendrick/nbs/unix/www/ssi/
Server Side Includes are commands ("directives") which the webserver looks
for as it is sending an HTML file from the server to the browser (client).
One SSI command, for example, inserts the contents of another file at
the position of the SSI. If you want all 500 of your HTML pages to have
the same copyright information, you can simply make all 500 pages "include"
a small file which contains the information. If you later need to update
or refine it, you only need to do it once, and all pages will, at that
point, appear with the new information. This is versus the overwhelming
task of changing 500 HTML pages by hand, or even with search-and-replace!!!)
Another SSI command, used here, actually executes a program and displays
its output at the position of the SSI. The "inchat" program simply
looks at how many people are in chat and then spits out that number.
In any HTML page on your server, you can specify an SSI command to
run the "inchat" program and automatically that page will then ALWAYS
show how many people are in chat at that very instant!
Here's how to use the "inchat" SSI:
SSI example: <!--#exec cmd="ssi/inchat"-->
HTML results: There are 3 people in chat.
There is one person in chat.
There are no people in chat.
SSI example: <!--#exec cmd="ssi/inchat -simple"-->
HTML results: 3
1
0
SSI example: <!--#exec cmd="../chatroom/ssi/inchat ../chatroom/who.dat"-->
HTML results: There are 3 people in chat.
There is one person in chat.
There are no people in chat.
By example, you can see that you can specify not only the relative path
of the SSI program "inchat", but also the location of the "who.dat" file
(which it reads to find out how many people are in chat.)
If the first "argument" of the SSI call is "-simple", then the words
"There are XX people in chat" is replaced with simply the number of
people. (If you need to specify the location of the "who.dat" file,
it will of course be the "second" argument if you specify "-simple"
as the first.)
For details on using the "random" SSI, please see the documentation
at: http://zippy.sonoma.edu/kendrick/nbs/unix/www/ssi/
== KNOWN BUGS ==
If a "convert" string is also part of a "convert" filename, the conversion
will die.
The swear word look-up doesn't work 100% correctly in all situations.
This is being looked into.
If you find other bugs, please e-mail me with specific details (number of
users, OS used, etc.) and your chat room's URL! kendrick@zippy.sonoma.edu
== THE NEXT RELEASE ==
The next release of Free Chat (date: TBA) will probably have more of the
planned features (see the Free Chat website), and will be much easier to
set up. Please add yourself to the Free Chat mailing list (see the website)
to keep informed on new releases!
== CREDITS / THANKS ==
Credits for Beta 2 release (9/23/1997) of Free Chat:
+ Free Chat is (c) by Bill Kendrick, September 1996 to August 1997.
E-Mail: kendrick@zippy.sonoma.edu
Website: http://zippy.sonoma.edu/kendrick/
New Breed Software: http://zippy.sonoma.edu/kendrick/nbs/
Free Chat website: http://zippy.sonoma.edu/kendrick/nbs/unix/www/freechat/
Thanks to:
+ Smart Wine for encouraging me to write my first chat room,
+ Sterba Online for letting me write and test Free Chat on their site
and for helping with ideas and design implementation,
+ Ron Both for his comments and praise,
+ "Brian", "Emina", "Sis", "Reiner-shyn" and the many others who
patronize my chat room, helped with ideas, and sat through the crashes
while I used them as guinea-pigs ;^),
+ and thank YOU for trying out Free Chat!
END
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -