Difference between revisions of "Hybrid"
Jump to navigation
Jump to search
m (ratbox succession) |
|||
Line 1: | Line 1: | ||
http://img403.imageshack.us/img403/3562/hybridlogo.jpg | http://img403.imageshack.us/img403/3562/hybridlogo.jpg | ||
<Rating comment=false> | |||
Rate This! | |||
1 (Hate it) | |||
2 (Dislike it) | |||
3 (It's ok) | |||
4 (Like it) | |||
5 (Love it) | |||
</Rating> | |||
'''Website:''' | '''Website:''' | ||
Line 5: | Line 14: | ||
'''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 | * 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 Time Stamping 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. | ||
* Has been superseded by [[Ratbox]] as the EFNet IRCd. | * Has been superseded by [[Ratbox]] as the EFNet IRCd. | ||
Revision as of 22:28, 6 June 2010
<Rating comment=false> Rate This!
1 (Hate it) 2 (Dislike it) 3 (It's ok) 4 (Like it) 5 (Love it)
</Rating>
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 Time Stamping 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.
- Has been superseded by Ratbox as the EFNet IRCd.
Programming Language:
- C
Platform:
- BSD Linux Windows
License:
- GPL
Supported IRC Services:
- Anope
- Atheme
- ChanFix
- IRC Services
Supported Extended Services:
Latest Stable Release: 7.2.3 and the tar.gz can be downloaded Here