Since you unpacked this you probably want to install it.
You can go straight to the INSTALL.txt file for instructions.
If it is missing, try http://www.psyced.org/INSTALL.html



		PROTOCOL for SYNCHRONOUS CONFERENCING
	    ___   __  _   _   __    _    _ _  _ _   _ ___
	    |  \ (__   \ /   /      |\  /| |  | |   | |
	    |__/    \   V   |       | \/ | |  |  \ /  |-
	    |    (__/   |    \__    |    | |__|   V   |__

	  The MULTI USER VIRTUAL ENVIRONMENT driver is here!
	    =============================================



This is 'psyced', the Multi User Virtual Environment for PSYC.
It is a server and gateway implementation of PSYC.

The latest version is available on http://www.psyced.org/download

There is no download by FTP, since FTP has no advantage
over HTTP/1.1 (you can use HTTP REGET these days).

The project homepage is http://www.psyced.org
The protocol homepage is http://www.psyc.eu
The user manual resides at http://help.pages.de

The Multi-User Virtual Environment for PSYC-Users isn't just a PSYC server;
it also simulates the functionality of PSYC clients allowing users of various
sorts of more or less dumb applications to enter the PSYCspace.

The professional edition of it has been in use as a Webchat for several years.
The HTML webchat, however, is not part of the freeware edition.

psyced is implemented in LPC and uses a driver called LDMUD.
Why LPC you ask? http://about.psyc.eu/LPC
See INSTALL for details.

The files in the distribution directory are:
  AGENDA.txt	: future plans (not a TODO really)
  BANNER.txt	: advertisement or welcome message
  COPYLEFT.txt	: GNU GENERAL PUBLIC LICENSE
  INSTALL.txt	: installation hints and notes
  LICENSE.txt	: something you are supposed to read (copyright info)
  README.txt

  install.sh	: an installation script (ksh/bash).
  makefile	: some useful functions (optional).
  bin/		: various scripts
		  but the only one you really need, "psyced",
		  will be created by 'install.sh'.
  config/	: depot of configurations.
		  also contains some tcsh and powwow settings.
  data/		: this is where psyced stores your user and room data.
  local/	: your local configuration of the server
		  is created by 'install.sh' but you can also make
		  it a symlink into a config/something directory
  log/		: where the server logfiles end up.
		  may be a symlink into the /var partition.
  place/	: here you can implement your own room objects in lpc.
                  some examples of public rooms are waiting for you there.
  run/    	: the ldmud equivalent of a CGI directory. ldmud can spawn
		  a subprocess to do some jobs which are too hard to achieve
		  in LPC-world. we currently don't use this as ldmud provides
		  MD5 and SHA1 itself. in theory we could implement CGI for
		  the builtin webserver, but it is much better to code these
		  things in LPC. world/net/jabber/component.c shows how sha1.pl
		  is spawned when the driver does not provide SHA1.
  utility/	: the applet code and other things that may be useful.
  world/    	: this is the directory tree that is visible from
                  within the lpc interpreter and therefore contains
                  all the actual lpc program code.
       data/		: symlink to data/
       default/   	: the text database for multiple languages and formats
       drivers/   	: glue code to interface LPC drivers to psyced
       local/		: symlink to local/
       log/		: symlink to log/
       net/		: all of the psyced code is in a "net" hierarchy
			: so it can be merged with an existing MUD
       obj/		: just in case you misconfigured your driver
       place/		: symlink to place/
       static/   	: contains static files for httpd export
			: you can use them with the internal httpd
			: or copy them to yours

Don't be irritated by the fact that traditional LPC drivers keep
their LPC files with a ".c" suffix and data files with a ".o" suffix.
More oddities are described in http://www.psyced.org/DEVELOP if you want
to find your way around the psyced source code.

________________________________________________________________________
== MAJOR SHORTCOMINGS in 0.99 ==  .. probably belongs into README.pht ==
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
This section is about the architectural and other shortcomings of the
current psyced release.
We know about these problems, we will fix them in the future but we
do not think they are critical enough to stop us from releasing, since
there are many other jobs psyced is doing very well.

* PSYC clients have to deal with some serious shortcomings. The only
  client who does so pretty well is psycion. But still some architectural
  corrections are necessary to really allow for PSYC clients.

The PSYC protocol as such however is in a pretty good shape except for
the client-to-server bit, so if you're looking into implementing servers
or gateways, the time is right!

* JABBER client access is experimental and might misbehave. We are working
  on this, but so far our priority was to have Jabber interserver
  communication work well.

  One particular shortcoming: It is as yet not possible to connect more
  than one Jabber client to an identity. This is an architectural issue
  in psyced which is to be fixed. Ironically you can connect as many
  PSYC clients as you need, but they're not ready to go.