Free irc servers software for linux

Faerion IRC Server project consists of an advanced, secure, multi-lingual IRC server for Unix/Win32.
Faerion is a Unicode-based IRC server. It features enhanced support and transparent conversion for different charsets, and provides a stealth network model, persistent channels, compressed links, etc.
Main features:
- Support for transparent, user-controlled charset translation (virtually) from anything to anything. This is done by using Unicode mappings, which can be installed or removed on the fly, without having to interrupt the server. The server supports a special "fallback" conversion table which maps all characters that are not supported by a users preferred charset to the closest looking characters. This process is typically referred to as "transliteration" and is widely used on Russian IRC networks to avoid problems with incompatible charsets. The difference is that with Faerion, the server takes all necessary investigation to see what should be transliterated, and what can be passed without changes.
- Clients that have native support for Unicode (UTF-8), will benefit from using it at full scale without the implication of "cryptic writings" (which raw UTF-8 is for a typical human eye).
- Support for "persistent channels": channels registered with the Channel Service (mode +r) are not deleted when the last user leaves. This slightly saves bandwidth and helps mitigate several privacy issues (such as channel key revelation).
- Support for channel forwarding based on user address matching rules: with channel mode +f enabled, all ban masks can have a ",#channel" suffix appended to them to forward clients to another channel instead of declining the attempt to join the channel.
- Limited portability. The server is currently available for most POSIX platforms (modern BSD and Linux variants) and Microsoft Windows.
Enhancements:
- The LIST command now requires users with unregistered nicknames to additionally specify a pseudo random number to prove their human nature, otherwise the command is ignored.
- Opers no longer need an O-line to use any command; remotely set +o works just fine.
- Fixed the charset conversion problem when a user gets registered on the server.
- Invite list no longer overrides ban list.
- Fixed a crash in WHOIS.
- Fixed to compile without warnings in -Werror mode with GCC 3+.
- Fixed the +c channel mode to disallow colors instead of stripping them.Also, when a topic is being changed by a nonop on a +c-t channel to something that contains colors, the attempt is denied.

ServerSpyIRC project is an IRC bot to get information about online Quake2, Quake3, and Halflife servers.

ServerSpyIRC is a Perl IRC bot (based on Net::IRC) which can retrieve information about Quake2, Quake3, and Halflife/CS online game servers.

It supports many search functions, scanning of posted IP addresses, simple clanwar outputs, user management, bookable functions, and server lists.

First, there is a daemon (ircbase) that runs on a Unix server and performs actual IRC client operations. It listens on an assigned TCP port for connections from the actual user, which will run another program. This other program (irc.exe for now) can run on Windows, and prThere is now limited support for connecting with conventional IRC clients.Povides graphical user interaction to the features contained in ircbase.
There is now limited support for connecting with another IRC clients. Such a solution will not be able to take full advantage of the features in ircbase, and is also currently rather flakey and ad hoc, but its provided anyway for people that want it while they wait for the native clients to be usable enough. When you do this, ircbase will behave like an advanced autonomous detachable ircbouncer.
Set up your IRC client to connect to the ircbase like it was an IRC server. The nick you setup in the client will map to ircbase session ID, and ircbase will connect to the actual IRC server with the session parameters (including nick) from the configuration file. It will then do some tricks to convince the IRC client of the actual nick in use after connecting/attaching, to avoid confusing it.
(The nick is used to select session ID rather than anything else in order to make it easy to use with ircII, which can specify the nick on the command line or in the /server and /window server commands.)
If you need to issue a command for interpretation by the ircbase parser, you can prefix it with /QUOTE I, e.g. for accepting a DCC on the ircbase end, use /QUOTE I /dcc get nick
and for changing servers, /QUOTE I /server irc.server
Main features:
- The above structure has the advantages that you can run ircbase on a shell account (warning, advertisement: Arctic Net can provide these) idling permanently on the IRC server very much like a bot, and yet, the user can, whenever he comes online, and from wherever he is, connect to it and use it for IRC-ing like any other IRC client.
-
- The ircbase keeps track of the most recent events, so when he does this, he will automatically receive its "scrollback buffer", so he can quickly catch up with what has happened just before he arrived. This is also an advantage if his modem is unstable and often drops the connection, since this way he wont miss anything, no matter how thoroughly the user machine itself crashes (provided he comes online again before the buffer is completely flushed, of course, but this buffer can be arbitrarily sized).
-
- Since ircbase allows scripts to run unattended at all times, it is meant to be able to replace any dedicated bots. Bots are a menace to the net, with their use of resources better spent on human clients, and the net would do so much better without them. With this system, even the most diehard childish moronic obnoxious bot-lover can do without them, simply because our design is superior, when completed.
-
- A system for interconnecting ircbases into an op-net (to replace the traditional bot-net) is also planned.
Enhancements:
- Finally gave a license to ircbase (irccli is still undecided, though).
- Finally ircbase is now under the GNU General Public License, version 2.

MetalServe provides a standalone IRC DCC file server.

MetalServe is a standalone DCC file server that can be used to share files on Internet Relay Chat (IRC) networks such as EFNet and Undernet. Unlike the only available similar Unix program, iroffer, which offers "packs" of files, MetalServe offers single files similar to the way the SDFind, SPRJukebox, and OmenServe scripts for mIRC, a Windows IRC client, work.

The motivation for writing this program arose because the masquerading Linux router between my desktop IRC client and the IRC servers in the Internet made sending files even harder than getting files. Additionally, the router was hosting the files to be offered anyway, so why not let the serving application run on the router as well. However the only available application as of the time of this writing (April 2002) was iroffer, which, as mentioned, operates in a different manner than desired.

I took a look at the available IRC clients and their scripting capabilities but in the end "standard" ircII 4.4M, BitchX, Epic etc. didnt look powerful enough, had too many security holes etc. and various other aspects, including speed and independency, gave me reason enough to write a dedicated server application in C. In other words, I preferred the "precision screwdriver" approach.

IRC-Chess project is a 2-player chess game for IRC which turns a computer into an IRC chess bot.

It consists of a Java chess server, with frontend scripts to convert an IRC client into a chess bot. Players then communicate with the bot using standard IRC commands, and dont require any special software to play.

Frontend scripts are available for IRSSI and X-Chat.

The client is merely responsible for interpreting this data and displaying it. In this way, porting the system to a variety of IRC clients is very simple, since
the client script will be short, and effectively contain no code specific to the game being played.

In other words, the Java part is smart. The script is dumb and is just there to make things look pretty.

This idea works. Currently, client scripts have been designed for RSSI and XChat. Since both these programs use Perl for scripting, the scripts are practically identical, with a few client specific modifications.

Porting this script to other IRC clients shouldnt be too much of a hassle, since its just the frontend thats ported, not the chess game itself. Anyone wanting to create frontend scripts for other IRC clients, please feel free to do so.

The PROTOCOL file describes exactly what needs to be done.

irclogger is a simple "bot", a program connecting as a client on IRC servers to provide a web log of what is said. It is built to provide a simple and web-compliant service.
Irclogger was done to:
- Be used on intranets, where users can be trusted and will not try constantly to crack the system. Thus the bot do not need to provide the plethora of anti-hackers, channel defending measures
- Provide privacy, users can set passwords on the log files, change them, but cannot remove them
- Be another web tool, the bot obey just the minimal IRC commands to log or not a channel. All the rest is done via a web browser. Each logged phrase becomes a part of the web with its own URL.
I could not find a bot satisfying these criteria. All were huge monsters with bloated functionalities of dubious utility, many were disgusting amounts of ugly perl code.
I stumbled on a nice unfinished python bot "logger" by Sean B. Palmer and Dan Connolly, so I used it as a base for irclogger, and added html view of the logs.
irclogger consists of 2 parts:
- irclogger, a python IRC client writing text logs in the MIRC format.
- CGI shell scripts, (bash) to be used from a web server to format the logs into html and provide searching in them.
Enhancements:
- Bugfix for python 2.3:
- Crashed when somebody said in a channel: [LOGGER], off the format of args passed to the function had changed
- Crashed when no more channels were logged
- Would not remove a channel from the list of logged chans for next time when kicked out of it

Relay-bot is a program we initially wrote because our group of friends that hang out on one channel could never seem to all stay on EFnet, and even if we could EFnet was splitting so badly at the time that it was unusable. However, we couldnt readily switch to another network because not everybody is always online and a few people wanted to stick with EFnet because there were other friends of theirs still there. So, relay-bot was born. It allowed us to split our channel across 2 (actually, 3 or 4) different IRC networks fairly effectively.
You[l need a copy Of Perl since perlay bot is written in Perl. Youll also need a copy of Net::IRC.
Theres currently no real installation routine; just untar the tarball, edit "relay-bot.config" and run "relay-bot.pl".
Enhancements:
- relay-bot.config: Fixed small issue in example config file
- BUGS, relay-bot.pl: Prepping for update to a new release