Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
service:ircd [2010/02/26 09:38] – Further changes cyanservice:ircd [2018/12/20 17:00] – [Introduction] tobe -> to be wkitty42
Line 4: Line 4:
  
 The Synchronet IRCd (IRC daemon) service is a static service written in 100% Javascript.  It's currently the largest (and perhaps The Synchronet IRCd (IRC daemon) service is a static service written in 100% Javascript.  It's currently the largest (and perhaps
-the most complex) service available for Synchronet.  The IRCd service aims tobe a 'communications bridge' of sorts which will allows multiple BBS's to link together in a network so that users may talk to one another from the comfort of their home BBS or IRC client.  The Synchronet IRCd is a fully-functional IRC daemon that rivals the bigger, legacy UNIX IRC daemons in terms of features.  This way, everyone who wishes to chat on a common network will be able to use the local BBS, or a standard IRC client (if they wish.)+the most complex) service available for Synchronet.  The IRCd service aims to be a 'communications bridge' of sorts which will allows multiple BBS's to link together in a network so that users may talk to one another from the comfort of their home BBS or IRC client.  The Synchronet IRCd is a fully-functional IRC daemon that rivals the bigger, legacy UNIX IRC daemons in terms of features.  This way, everyone who wishes to chat on a common network will be able to use the local BBS, or a standard IRC client (if they wish.)
  
 ====== About this document ====== ====== About this document ======
Line 148: Line 148:
 - Private/Secret channels are not revealed to the leaf unless a user on the leaf explicitly joins the channel. - Private/Secret channels are not revealed to the leaf unless a user on the leaf explicitly joins the channel.
  
-[5.3] - Compatibility with other IRCd's+====== Compatibility with other IRCd's ======
  
- The Synchronet IRCd has only been tested to be link compatible with:+The Synchronet IRCd has been tested to be link compatible with:
  
  * Bahamut 1.4.35, 1.4.36 http://bahamut.dal.net  * Bahamut 1.4.35, 1.4.36 http://bahamut.dal.net
Line 159: Line 159:
 ====== The Future ====== ====== The Future ======
  
- Although the original intention of the IRCd was to allow users to +Although the original intention of the IRCd was to allow users to interact between one another from the BBS multi-node chat area, that has yet to occur.  Eventually, users will be able to talk to one another from various BBS's and not even be aware that they're using IRC as the transport protocol for their chat sessions.  For the time being, one can use the Synchronet IRC client (irc.js) to connect to their local IRC server.
-interact between one another from the BBS multi-node chat area, that has yet +
-to occur.  Eventually, users will be able to talk to one another from various +
-BBS's and not even be aware that they're using IRC as the transport protocol +
-for their chat sessions.  For the time being, one can use the Synchronet IRC +
-client (irc.js) to connect to their local IRC server.+
  
- Further compatibility with the later Bahamut daemons is planned, +Further compatibility with the later Bahamut daemons is planned, including the server-to-server "RESYNCH" command.  Also, more umodes will be supported, in addition to the possibility of gaining some of the Bahamut channel modes (i.e. +c)  Exception modes (+e, etc) and exception lines (to circumvent K:Lines) may be implemented.
-including the server-to-server "RESYNCH" command, user-accessible "WATCH", and +
-"SILENCE."  Also, more umodes will be supported, in addition to the possibility +
-of gaining some of the Bahamut channel modes (i.e. +c)  Exception modes (+e, +
-etc) and exception lines (to circumvent K:Lines) may be implemented.+
  
- Some sort of mechanism will be implemented to allow individual BBS's +Some sort of mechanism will be implemented to allow individual BBS's to share their message and file areas over IRC.  This means that you'll be able to DCC send/receive files from a BBS, QWK packets, messages, and that sort of thing.
-to share their message and file areas over IRC.  This means that you'll be +
-able to DCC send/receive files from a BBS, QWK packets, messages, and that +
-sort of thing. +
- +
- I'm sure DigitalMan has a ton of cool ideas, too ;)+
  
 ====== Frequently Asked Questions ====== ====== Frequently Asked Questions ======
- 
-[7.1] - Installation Questions 
  
  Q: After setting up my IRCd, and trying to connect, it gives me an  Q: After setting up my IRCd, and trying to connect, it gives me an
Line 250: Line 234:
     would execute the command like this: '/OPER Sysop <syspass>'.     would execute the command like this: '/OPER Sysop <syspass>'.
     Also check out the O:Line section in ircd.conf.     Also check out the O:Line section in ircd.conf.
 +
 + Q: I've been forced off of the server with a "Terminated." message.
 +    What does this message mean?
 +
 + A: This message is an indication that the Sysop of your BBS/IRCd has
 +    shut down the BBS, and the IRCd is terminated as a result of that.
 +    It is an indication of explicit termination (i.e., the IRCd was
 +    instructed to shut down by a human being).
  
  Q: My question isn't answered in this document, where can I go?  Q: My question isn't answered in this document, where can I go?

Trace: