hapkomah
02-05-2003, 02:31 AM
We was develop project. It is a ADBOT, but it is looking like real guy on chat. Some info about this project:
The system is based on a client-server architecture and thus consists of two parts: the Linux Server and Win32 Clients. Server comprises two subsystems: the Chat Bot and the Protocol Support modules.
Chat Bot is a module which generates answers for the sentences it is asked. It can also initiate talk. The bot has its own personality: name, age, sex, location, hobbies and so on. All of these parameters can be configured on the server side for each customer of our system. There are also a number of bot's timing parameters such as private chat open delay, the bot's typing rate, the delay between advertisement, etc. Some of these values are random number between bounds we set in the customers profile, some are the exact numbers. Our customers should not care about this because bot tuning is performed by Bot Administrator. Customer should only send him the complete description of the virtual person he want to have as his advertisement agent.
So customer gets a virtual man which can talk with other people periodically saying them an advertisement. The set of these messages is stored in the customer's profile on the server. There is also a flexible system which can introduce advertising messages as a part of talk. For example, bot says: “do you have a cat?”. Then if his interlocutor answers he does, bot promotes cats food. Otherwise bot just continues the chat. So bot doesn't spam people. It looks like a real person, thus effect of such promoting is very high.
The second subsystem – Protocol Support modules – is a common interface to various IRC-style Internet chat systems. Currently we support only gay.com chat protocol. Others will come soon.
The Win32 Client is a small client-side program intended for customer authentication, informing, and for network connection forwarding. The latter is vital because we must hide real IP of the server from chat systems administrators. All traffic between Client and Server is compressed, so it is not very high. Our system supports clients behind SOCKS proxy or NAT. Client also support auto-reconnecting when experiencing a connection problems.
And we are looking for ways for getting money back now...
Since we are in Russia, we cannot accept checks from affiliate programs. We will spam your site throughout the chat rooms and you will receive the checks and send us a % or we can sell this service for you
If you have some additional ideas about this project, please reply me too
PS. Sorry for my English, I'm from Russia.
Email: hapk@sh.ru, ICQ 73761924
The system is based on a client-server architecture and thus consists of two parts: the Linux Server and Win32 Clients. Server comprises two subsystems: the Chat Bot and the Protocol Support modules.
Chat Bot is a module which generates answers for the sentences it is asked. It can also initiate talk. The bot has its own personality: name, age, sex, location, hobbies and so on. All of these parameters can be configured on the server side for each customer of our system. There are also a number of bot's timing parameters such as private chat open delay, the bot's typing rate, the delay between advertisement, etc. Some of these values are random number between bounds we set in the customers profile, some are the exact numbers. Our customers should not care about this because bot tuning is performed by Bot Administrator. Customer should only send him the complete description of the virtual person he want to have as his advertisement agent.
So customer gets a virtual man which can talk with other people periodically saying them an advertisement. The set of these messages is stored in the customer's profile on the server. There is also a flexible system which can introduce advertising messages as a part of talk. For example, bot says: “do you have a cat?”. Then if his interlocutor answers he does, bot promotes cats food. Otherwise bot just continues the chat. So bot doesn't spam people. It looks like a real person, thus effect of such promoting is very high.
The second subsystem – Protocol Support modules – is a common interface to various IRC-style Internet chat systems. Currently we support only gay.com chat protocol. Others will come soon.
The Win32 Client is a small client-side program intended for customer authentication, informing, and for network connection forwarding. The latter is vital because we must hide real IP of the server from chat systems administrators. All traffic between Client and Server is compressed, so it is not very high. Our system supports clients behind SOCKS proxy or NAT. Client also support auto-reconnecting when experiencing a connection problems.
And we are looking for ways for getting money back now...
Since we are in Russia, we cannot accept checks from affiliate programs. We will spam your site throughout the chat rooms and you will receive the checks and send us a % or we can sell this service for you
If you have some additional ideas about this project, please reply me too
PS. Sorry for my English, I'm from Russia.
Email: hapk@sh.ru, ICQ 73761924