Free irc icq chat rooms software for linux

ICMP-Chat is a simple console-based chat that uses ICMP packets for communication. All the data is encrypted with Rijndael-256 algorithm.
Installation:
Type: make && make install
For solaris type: make solaris && make install
Usage:
Usage: icmpchat [OPTIONS] < host > < nick >
< host > = Host to chat with
< nick > = Your nickname
OPTIONS:
-t < type > = specify icmp type (default ECHO_REPLY)
Example: icmpchat 192.168.1.2 foo
ICMP codes:
[0] Echo Reply
[5] Redirect
[8] Echo Request
[9] Router advertisement
[10] Router solicitation
[13] Timestamp request
[14] Timestamp reply
[15] Information request
[16] Information reply
[17] Adressmask request
[18] Adressmask reply
Enhancements:
- Rewrote from scratch
- Implemented optimized rijndael algorithm
- Implemented sha256 for password hashing
- Implemented ncurses frontend (again)
- Fixed getuid problem so that setting suid flag works now (thanks John)

ARSC Really Simple Chat is a Web chat system that uses PHP and MySQL.
ARSC Really Simple Chat project works with every browser in existence, even text-based ones, and it uses the server push technique or, if possible, its own socket server.
It is very simple to install and use ARSC. It includes some important features, such as operators, kick-ing, whispering, and more.
Multiple rooms and different languages are available. To run ARSC on your site, you need a Web server that understands PHP, and can connect to a MySQL database.
Main features:
- very easy installation
- multiple languages supported
- multiple browsers/platforms supported (even text-based ones)
- comfortable administration interface
- private rooms
- two-leveled moderation system with message queue and Moderator/VIP roles
- graphical smilies
- freely definable layouts, with different layouts possible for individual rooms and/or users
- ID-Cards for registered users, with individual guestbooks on every ID-Card
- text-browser interface even allows chatting with braille screen readers
- security: uses sha1 hashes for passwords and sessionids, and every single user input is checked against a regular expression of allowed values
- works with PHP 4 and PHP 5
- works with safe_mode = On and register_globals = Off
Once installed on your webserver, ARSC provides a chat interface to the visitors of your site. Your visitors need no special plugins or additional software to chat, only their webbrowser. ARSC is licensed under the GPL, which means it is free (like in "free speech"). It also comes at no cost (like in "free beer"). You may even use it in your own software projects.
Chatting with ARSC is very comfortable. If you have a modern browser with frame support and JavaScript support enabled, ARSC makes use of these technologies. If you have an older browser, or you have JavaScript disabled, or even if you have a browser that does not support frames, you can still chat with ARSC. Let me say it this way: With ARSC, chatting on a webpage is possible with every known browser under the sun that is still in use nowadays.
In contrary to many other PHP/MySQL webchats, ARSC can be run using a non-forking socketserver to handle all message transport. Other chats use the httpd process to handle the message transport, what causes a big overhead, while the socketserver of ARSC works very ressource-friendly and can handle way more users. The server is completely written in PHP and thus does not need any special requirements besides a cgi-bin installation of PHP 4.1.0 or above. Current versions of PHP (4.3.x) have been tested and work. If you are not able to compile a cgi-bin version of PHP or you may not start a socketserver on your machine, ARSC still offers the traditional message handling via the httpd process or even via meta refresh.
Enhancements:
- A bug that broke the installation routine was fixed.

Campus Chat Server project is a chat server intended for use in the Cadiz University campus network.
Enhancements:
- hash_maps are now used instead of maps, so the cost of lookup or insertion is O(1) in the average case, instead of O(logn).

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.

Voc is a stream-chat engine which is designed to work on high-loaded chat-servers. It is written in PHP, but uses Perl or C++ for Voc-daemon -- the special program to handle multiple user-connections. With Voc you can make a chat that will serve many conversations simultanously. And its html-based, so your chatters can use it from almost any browser.
The Voc-engine includes a lot of features so it will be interested not only for a big chat owners.
Whats so special about Voc-engine?
There are 2 classes of html-chats. Classic-type, with refreshing messages-window, And stream-type.
Refresh-type is known to everybody, so lets think about streams. What is the common way to introduce such functionality? Webmasters make cgi-script (PHP-script, jsp-srcpt, e.t.c) which checks for new messages every second (2,3...) and prints something to the client. Of course, you need one instance of the script for each client. Now calculate how many data-requests you need to process every second... At least two for each client -- get messages, get users-list.
Also dont forget about memory and CPU usage. For instance, if you have PHP-scripts and PHP is compiled as an Apache-module, be ready to spend 5 Mbytes of memory and 0.1-1% of CPU for each client (only for messages-window).Multiple it to number of users online.
Do you still want to use such scripts?
Is there any solutions? I guess, yes -- try Voodoo chat. It uses Perl- or C++-daemon which processes users-requests to a messages list. And you need just one daemon for all clients. This daemon takes approx. 10 Mbytes of memory for 100 users. CPU usage is also small (of course it depends on your CPU, i.e. for 100 users online it is 0.5% of Pentium 4 2.4 Ghz). Do you see the difference now?
Main features:
- Daemon-stream type (recommended)
- Classic-type (with refreshes)
- PHP-stream script (read text above and use this type only when you have less then 20 simultaneous visitors and cannot use daemon-type)
- JavaScript stream-emulation (refreshing hidden frame which just add text to the main message-window)
- Themes-support. You can use one of exisitng designes, or easily create your own
- rooms
- private messages
- ignoring
- you can enable to use bold, italic, underlined messages
- inline images
- personal info-page with photo for registered users
- avatars
- internal mini-mail system
- status (online/offline/not available/dont disturb)
- web-indicator (see example at the left)
- nick & string highlighing for personal messages
- anti-flood
- messages and ban/unban logging
- limits for maximum number of users and maximum number of users from one ip (anti-nick-flooding)
- graphical statistic, example
- admin-zone to manage the chat
- moderator-levels for registered users, so you can give someone permissions to ban/unban users, change rooms-info, edit/delete registered users

MWChat Basic (My Web based Chat) is the free version of our online chat system.

Licenses are IP based, one license per IP.

It has support for multiple rooms and languages, a large number of IRC-like commands, private messages and rooms, message encryption, buddy lists, logging, registered users, chat profiles, file sharing, and more. It is a very lightweight, full-featured, and secure chat room.

The UbuntuLiveChatSupport aims to provide an interface to communicate to other ubuntu users with the same language & location, as well as to connect to the official ubuntu channel in Freenode.org. Ubuntu Live Chat Support also aims to get live chat support from ubuntu users right into the desktop menu, via "System > Help > Live Chat Support".
Rationale
People who dont speak english and want local support in their language will face a challenge to gain help in existing documentations, specially when there are just a few documentations for their language. But if they speak to someone that can understand their language, they can talk to an experienced user to provide them with answers. It might as well be positive, because there might be a good chance that they will collaborate on translation of documentations and software for their language, as well as contributing to the Ubuntu work.
Another problem with the current way of getting help in Ubuntu requires the user to read and browse documentations, but what most users really want is getting the right answers to the questions straight. Browsing and reading documentations sometimes require one to research on a particular problem. But to get the right answer from an experience user is the most easiest way.
Scope
This will use Gaim as an IRC client, but will not alter the main Gaim configurations. It will add the IRC channels defined in InternetRelayChat in Gaim buddy list, namely, Localized Channels, Support Channels, and Team Collaboration Channels.
Enhancements:
- Change the name "Auto-Join Default" to "Default"
- Overhaul the Local Channel names
- A new channel will be autojoined based on language.
- Added the language to "Local Languages" group
- Change the name of "Local Ubuntu Channels" to "Local Channels"
- UI improvements, in Nick registration, add a "Passwords do not match" warning.
- Impliment a settings in login page to choose from 2 different layout, the default top channels tab and alternative left channels tab. The static xchat-gnome look is removed.
- Add a new checkbox for privacy, when registration.
- Impliment registration privacy when the checkbox is toggled.