Difference between revisions of "Hybrid"

From IRC Wiki
Jump to navigation Jump to search
m (Remove redundancy, fix tags)
Line 5: Line 5:


'''Bio:'''
'''Bio:'''
* When talking about the history of ircd-hybrid, we have to look backwards to the times of The Great Split (the split in 1996 which divided the original IRC network into EFnet and IRCnet). One of the technical arguments beyond this event was how an IRC daemon should deal with duplicated entities after servers are re-linked. Generally, further EFnet admins supported the idea of TimeStamping nicknames and channels (so that in normal case only the newer one is dropped). Time has proved that TS along with some nick/channel delay options can be a very good choice. it has been known to run on [IRC Services] and could also run with [Anope]
* When talking about the history of ircd-hybrid, we have to look backwards to the times of The Great Split (the split in 1996 which divided the original IRC network into EFnet and IRCnet). One of the technical arguments beyond this event was how an IRC daemon should deal with duplicated entities after servers are re-linked. Generally, further EFnet admins supported the idea of TimeStamping nicknames and channels (so that in normal case only the newer one is dropped). Time has proved that TS along with some nick/channel delay options can be a very good choice.


'''Programming Language:'''
'''Programming Language:'''
Line 17: Line 17:


'''Supported IRC Services:'''
'''Supported IRC Services:'''
* [Anope]]
* [[Anope]]
* [Atheme]]
* [[Atheme]]
* [IRC Services]]
* ChanFix
* [[IRC Services]]


'''Supported Extended Services:'''
'''Supported Extended Services:'''

Revision as of 15:58, 6 May 2010

hybridlogo.jpg

Website:

Bio:

  • When talking about the history of ircd-hybrid, we have to look backwards to the times of The Great Split (the split in 1996 which divided the original IRC network into EFnet and IRCnet). One of the technical arguments beyond this event was how an IRC daemon should deal with duplicated entities after servers are re-linked. Generally, further EFnet admins supported the idea of TimeStamping nicknames and channels (so that in normal case only the newer one is dropped). Time has proved that TS along with some nick/channel delay options can be a very good choice.

Programming Language:

  • C

Platform:

  • BSD Linux Windows

License:

  • GPL

Supported IRC Services:

Supported Extended Services:

Latest Stable Release: 7.2.3 and the tar.gz can be downloaded Here