├── .gitmodules ├── README.md ├── alien.net.au ├── chanmembers.def ├── chanmembers.html ├── chanmodes.def ├── chanmodes.html ├── chantypes.def ├── chantypes.html ├── irc2numerics.def ├── irc2numerics.html ├── ircinfo.css ├── servermodes.def ├── servermodes.html ├── usermodes.def └── usermodes.html ├── client ├── .links ├── CAP-drafts │ ├── 2002-draft-baudis-irc-capab-00.txt │ ├── 2003-client-cap.txt │ ├── 2005-draft-mitchell-irc-capabilities-01.html │ ├── 2005-draft-mitchell-irc-capabilities-02.html │ └── README ├── CTCP │ ├── ctcp-1997.html │ ├── ctcp-wboard.html │ ├── ctcp.html │ ├── ctcp.txt │ ├── ctcp2_1.html │ ├── ctcp2_2.html │ ├── ctcp2_3.html │ ├── ctcp2_4.html │ ├── ctcp2_5.html │ ├── ctcp2_6.html │ ├── ctcp2_intro.html │ ├── dcc-reverse.txt │ ├── dcc-turbo.html │ ├── troy-dcc.html │ └── xdcc-3.3.0b.irc ├── IRCX │ ├── docbook │ │ ├── apa.html │ │ ├── apas02.html │ │ ├── apas03.html │ │ ├── apas04.html │ │ ├── apas05.html │ │ ├── apas06.html │ │ ├── apas07.html │ │ ├── apas08.html │ │ ├── apas09.html │ │ ├── apas10.html │ │ ├── apas11.html │ │ ├── apas12.html │ │ ├── ch01.html │ │ ├── ch02.html │ │ ├── ch02s02.html │ │ ├── ch03.html │ │ ├── ch03s02.html │ │ ├── ch03s03.html │ │ ├── ch03s04.html │ │ ├── ch03s05.html │ │ ├── ch03s06.html │ │ ├── ch03s07.html │ │ ├── ch03s08.html │ │ ├── ch03s09.html │ │ ├── ch03s10.html │ │ ├── ch03s11.html │ │ ├── ch03s12.html │ │ ├── ch03s13.html │ │ ├── ch04.html │ │ ├── ch04s02.html │ │ ├── ch04s03.html │ │ ├── ch04s04.html │ │ ├── ch04s05.html │ │ ├── ch04s06.html │ │ ├── ch04s07.html │ │ ├── ch04s08.html │ │ ├── ch05.html │ │ ├── ch05s02.html │ │ ├── ch06.html │ │ ├── ch06s02.html │ │ ├── ch07.html │ │ ├── ch07s02.html │ │ ├── ch08.html │ │ ├── ch09.html │ │ ├── ch10.html │ │ ├── ch11.html │ │ ├── index.html │ │ ├── ircx-draft.css │ │ ├── pr01.html │ │ ├── pr02.html │ │ └── pr03.html │ ├── draft-pfenning-irc-extensions-04.dump.txt │ ├── draft-pfenning-irc-extensions-04.html │ └── draft-pfenning-irc-extensions-04.txt ├── IRCplus │ ├── .links │ ├── irc-plus │ │ ├── .links │ │ ├── confctrl-draft.html │ │ ├── identity-draft.html │ │ ├── index.html │ │ ├── main.css │ │ ├── specs.html │ │ └── subscriptions-draft.html │ └── psyc.eu-IRCPLUS.html ├── RPL_ISUPPORT │ ├── _html │ │ ├── draft-brocklesby-irc-isupport-00.html │ │ ├── draft-brocklesby-irc-isupport-01.html │ │ ├── draft-brocklesby-irc-isupport-02.html │ │ ├── draft-brocklesby-irc-isupport-03.html │ │ └── draft-hardy-irc-isupport-00.html │ ├── draft-brocklesby-irc-isupport-00.txt │ ├── draft-brocklesby-irc-isupport-01.txt │ ├── draft-brocklesby-irc-isupport-02.txt │ ├── draft-brocklesby-irc-isupport-03.txt │ ├── draft-hardy-irc-isupport-00.txt │ └── irc.org-tech_docs-005.html ├── SASL │ ├── DH-AES.md │ └── DH-BLOWFISH.md ├── SOURCE ├── cap-identify-msg.md ├── cap-sasl.txt ├── draft-meglio-irc-watch-00.txt ├── epic5-colors1.txt ├── epic5-colors2.txt ├── ircv3-pastebin-2246272.txt ├── modeg.hybrid.txt ├── modeg.txt └── monitor.txt ├── extensions.md ├── family-tree.txt ├── misc-notes.txt ├── misc ├── IRC_UND1.FAQ ├── IRC_UND2.FAQ ├── PTlink-vlinks.txt ├── Persistent_Clients.txt ├── SOURCE ├── atheme-plus.html ├── atheme.IRCD ├── bahamut-server-version-info.txt ├── bitnet │ ├── SOURCE │ ├── relay-chat_vmcms-help.html │ ├── relay-faq.html │ ├── relay-history.html │ ├── relay-info.html │ ├── relay-rules.html │ ├── relay-smart_vcms-hints.html │ ├── relay-smart_vmcms-commands.html │ ├── relay-usage.html │ └── relay-xyzzy_vms-help.html ├── draft-brocklesby-irc-usercmdpfx-02.html ├── freenode-2006 │ ├── BreakageSlash.html │ ├── FreenodeRegistryDiscussions.html │ ├── Freenode_Registry.html │ ├── HyperionNOIDPREFIX.html │ ├── HyperionNOIDPREFIXPurpose.html │ ├── Talk:HyperionNOIDPREFIXPurpose.html │ └── TraditionalIRCUsers.html ├── hybrid-server-version-info.txt ├── irc-documentation-jilles │ ├── .hg │ │ ├── 00changelog.i │ │ ├── branch │ │ ├── cache │ │ │ ├── branchheads │ │ │ └── tags │ │ ├── dirstate │ │ ├── hgrc │ │ ├── requires │ │ ├── store │ │ │ ├── 00changelog.i │ │ │ ├── 00manifest.i │ │ │ ├── data │ │ │ │ ├── architecture.txt.i │ │ │ │ ├── channel management.txt.i │ │ │ │ ├── client protocol.txt.i │ │ │ │ └── reference │ │ │ │ │ ├── 1459.txt.i │ │ │ │ │ ├── 2810.txt.i │ │ │ │ │ ├── 2811.txt.i │ │ │ │ │ ├── 2812.txt.i │ │ │ │ │ ├── 2813.txt.i │ │ │ │ │ ├── draft-hardy-irc-isupport-00.txt.i │ │ │ │ │ ├── draft-meglio-irc-handshake-00.txt.i │ │ │ │ │ ├── draft-meglio-irc-watch-00.txt.i │ │ │ │ │ ├── draft-mitchell-irc-capabilities-02.txt.i │ │ │ │ │ ├── modeg.txt.i │ │ │ │ │ ├── monitor.txt.i │ │ │ │ │ └── snomasks.txt.i │ │ │ ├── fncache │ │ │ ├── phaseroots │ │ │ ├── undo │ │ │ └── undo.phaseroots │ │ ├── undo.bookmarks │ │ ├── undo.branch │ │ ├── undo.desc │ │ └── undo.dirstate │ ├── architecture.txt │ ├── channel management.txt │ ├── client protocol.txt │ └── reference │ │ ├── 1459.txt │ │ ├── 2810.txt │ │ ├── 2811.txt │ │ ├── 2812.txt │ │ ├── 2813.txt │ │ ├── draft-hardy-irc-isupport-00.txt │ │ ├── draft-meglio-irc-handshake-00.txt │ │ ├── draft-meglio-irc-watch-00.txt │ │ ├── draft-mitchell-irc-capabilities-02.txt │ │ ├── modeg.txt │ │ ├── monitor.txt │ │ └── snomasks.txt ├── ircd-hybrid-7.0-vchans.txt ├── kalt-irc │ ├── TS-Delay.html │ ├── channel.html │ ├── collisions.html │ ├── faq.html │ ├── index.html │ └── kills.html ├── kline.txt ├── ora-relative-chanops.txt ├── rfc1459.txt ├── rfc2812.txt ├── rfc2813.txt ├── services.txt ├── vchans.txt └── voting.efnet.org │ ├── archives │ ├── 0001.shtml │ ├── 0002.shtml │ ├── 0003.shtml │ ├── 0004.shtml │ ├── 0005.shtml │ ├── 0006.shtml │ ├── 0007.shtml │ ├── 0008.shtml │ ├── 0009.shtml │ ├── 0010.shtml │ ├── 0011.shtml │ ├── 0012.shtml │ ├── 0013.shtml │ ├── 0014.shtml │ ├── 0015.shtml │ ├── 0016.shtml │ ├── 0017.shtml │ ├── 0018.shtml │ ├── 0019.shtml │ ├── 0020.shtml │ ├── 0021.shtml │ ├── 0022.shtml │ ├── 0023.shtml │ ├── 0024.shtml │ ├── 0025.shtml │ ├── 0026.shtml │ ├── 0027.shtml │ ├── 0028.shtml │ ├── 0029.shtml │ ├── 0030.shtml │ ├── 0031.shtml │ ├── 0032.shtml │ ├── 0033.shtml │ ├── 0034.shtml │ ├── 0035.shtml │ ├── 0036.shtml │ ├── 0037.shtml │ ├── 0038.shtml │ ├── 0039.shtml │ ├── 0040.shtml │ ├── 0041.shtml │ ├── 0042.shtml │ ├── 0043.shtml │ ├── 0044.shtml │ ├── 0045.shtml │ ├── 0046.shtml │ ├── 0047.shtml │ ├── 0048.shtml │ └── 0049.shtml │ ├── docs │ ├── chanfix-faq.html │ ├── services.int.shtml │ └── what-chanfix-does.txt │ └── proposals │ ├── jupes.int.txt │ └── spoof-proposal.txt ├── numerics.txt └── server ├── LazyLinks.txt ├── SOURCE ├── TS-Delay.html ├── espel-tsora ├── Undernet-TS.txt ├── announcement.txt ├── index.html ├── lets-do-TS.txt └── protocol.html ├── p10-beware.txt ├── p10-login-on-connect.txt ├── p10-nefarious2.txt ├── ts-capab.txt ├── ts-enc-cryptlink.txt ├── ts-encap.txt ├── ts-kln-unkln-cluster.txt ├── ts1.txt ├── ts3.txt ├── ts4-faq.txt ├── ts4.txt ├── ts5.txt ├── ts6-euid.txt ├── ts6-save-collision-fnc.txt ├── ts6-ufnc.txt ├── ts6.txt ├── ts6v7.txt └── ts6v8.txt /.gitmodules: -------------------------------------------------------------------------------- 1 | [submodule "ircu-proto-doc"] 2 | path = server/ircu-proto-doc 3 | url = git://undernet-ircu.git.sourceforge.net/gitroot/undernet-ircu/proto-doc 4 | [submodule "ircv3"] 5 | path = ircv3 6 | url = git://github.com/atheme/ircv3-specifications.git 7 | [submodule "server/sasl-sts-protocol"] 8 | path = server/sasl-s2s 9 | url = https://gist.github.com/8389307.git 10 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Collected IRC protocol documentation 2 | 3 | See also: 4 | 5 | * [IRCv3 specifications](https://github.com/ircv3/ircv3-specifications) 6 | * Daniel Oaks' 7 | -------------------------------------------------------------------------------- /alien.net.au/chanmembers.def: -------------------------------------------------------------------------------- 1 | /* $Id: chanmembers.def,v 1.5 2004/10/16 19:55:51 pickle Exp $ 2 | * 3 | * This file is Copyright (c) 2001,2002,2003,2004 Simon Butcher 4 | * 5 | * 6 | * This file is PUBLIC DOMAIN, to benefit the IRC developer community. If you 7 | * modify this file, please state your name and modifications here in order 8 | * for people to be able to distinguish between your version and this version. 9 | * 10 | * For more information or corrections, please contact the author. 11 | */ 12 | autogen definitions chanmembers; 13 | 14 | /* The following format is used through-out this file. The fields 'name', 15 | * 'prefixchar', and irc2_mode are manditory, the others may or may not exist. 16 | * 17 | * chanmembers = { 18 | * name = ""; 19 | * prefixchar = ""; 20 | * irc2mode = ""; 21 | * [ origin = ""; ] 22 | * [ when = ""; ] 23 | * [ contact = ""; ] 24 | * [ information = ""; ] 25 | * [ comment = ""; ] 26 | * [ conflict = "yes"; ] 27 | * [ obsolete = "yes"; ] 28 | * } 29 | * 30 | * The list below is ordered from least authoritative to most 31 | */ 32 | 33 | 34 | revision = "$Revision: 1.5 $"; 35 | lastupdated = "$Date: 2004/10/16 19:55:51 $"; 36 | 37 | 38 | chanmembers = { 39 | name = "VOICED"; 40 | prefixchar = "+"; 41 | irc2mode = "v"; 42 | origin = "RFC1459"; 43 | comment = "Channel member is voiced. They can speak while the " 44 | "channel is being moderated. Some implementations also " 45 | "allow them to speak when barred from access to the " 46 | "channel for some reason (such as being banned)"; 47 | }; 48 | 49 | chanmembers = { 50 | name = "HALF_OPERATOR"; 51 | prefixchar = "%"; 52 | irc2mode = "h"; 53 | origin = "Hybrid"; 54 | comment = "User is a channel half-operator, that is they have " 55 | "'half' the access of a full operator. Half-ops can kick " 56 | "unopped users, voiced users, set channel modes including " 57 | "+v, but not kick ops or deop ops. This leads to greater " 58 | "security on channels."; 59 | }; 60 | 61 | chanmembers = { 62 | name = "OPERATOR"; 63 | prefixchar = "@"; 64 | irc2mode = "o"; 65 | origin = "RFC1459"; 66 | comment = "User is a channel operator. They can kick users, change " 67 | "modes, set other users to operator (or lower) status, etc."; 68 | }; 69 | 70 | chanmembers = { 71 | name = "CREATOR"; 72 | prefixchar = "@"; 73 | irc2mode = "O"; 74 | origin = "RFC2811"; 75 | comment = "The user created the channel, but only used for '!' " 76 | "channels according to the RFC."; 77 | }; 78 | 79 | chanmembers = { 80 | name = "SERVICE"; 81 | prefixchar = "!"; 82 | irc2mode = "!"; 83 | origin = "KineIRCd"; 84 | contact = "kineircd@alien.net.au"; 85 | comment = "This is given only by servers or services. It should " 86 | "always be the highest ranking membership type in the " 87 | "channel, and denotes that the user with the membership " 88 | "status is a service. The intended use for this was to " 89 | "mark out which channel member is an official channel " 90 | "service, however other applications are also available."; 91 | }; 92 | 93 | chanmembers = { 94 | name = "FOUNDER"; 95 | prefixchar = "."; 96 | irc2mode = "u"; 97 | origin = "tr-ircd"; 98 | comment = "This is given to users when they are given 'founder' " 99 | "status on a channel, and should have a rank higher than " 100 | "a normal operator."; 101 | }; 102 | 103 | -------------------------------------------------------------------------------- /alien.net.au/chanmembers.html: -------------------------------------------------------------------------------- 1 | 2 | 14 | 15 | 16 | IRC Channel Membership Prefix List 17 | 18 | 19 | 20 | 21 | 22 | 23 |

24 | Red denotes a conflicting definition, gray for depreciated (however 25 | quite possibly still in use), and blue for OK. 26 |

Updates? Please Email me! 27 | Thank you!

28 | 29 | 35 | 41 | 47 | 53 | 59 | 65 |
P
r
e
f
i
x 30 |
Name 31 | M
o
d
e 32 |
Origin 33 | Comments 34 |
+ 36 | VOICED 37 | v 38 | RFC1459 39 | Channel member is voiced. They can speak while the channel is being moderated. Some implementations also allow them to speak when barred from access to the channel for some reason (such as being banned) 40 |
% 42 | HALF_OPERATOR 43 | h 44 | Hybrid 45 | User is a channel half-operator, that is they have 'half' the access of a full operator. Half-ops can kick unopped users, voiced users, set channel modes including +v, but not kick ops or deop ops. This leads to greater security on channels. 46 |
@ 48 | OPERATOR 49 | o 50 | RFC1459 51 | User is a channel operator. They can kick users, change modes, set other users to operator (or lower) status, etc. 52 |
@ 54 | CREATOR 55 | O 56 | RFC2811 57 | The user created the channel, but only used for '!' channels according to the RFC. 58 |
! 60 | SERVICE 61 | ! 62 | KineIRCd 63 | This is given only by servers or services. It should always be the highest ranking membership type in the channel, and denotes that the user with the membership status is a service. The intended use for this was to mark out which channel member is an official channel service, however other applications are also available. 64 |
. 66 | FOUNDER 67 | u 68 | tr-ircd 69 | This is given to users when they are given 'founder' status on a channel, and should have a rank higher than a normal operator. 70 |
71 |
Return to the index 72 | 73 | 74 | -------------------------------------------------------------------------------- /alien.net.au/ircinfo.css: -------------------------------------------------------------------------------- 1 | table { background-color:#888888; width:100%; } 2 | thead { font-family:Arial; font-size:80%; vertical-align:text-bottom; } 3 | tbody { font-size:90%; } 4 | /* th.vert { width:1em; writing-mode: tb-rl; } */ 5 | tr { background-color:#DDDDFF; } 6 | tr.o { background-color:#DDDDDD; } 7 | tr.c { background-color:#FFDDDD; } 8 | tr.head { background-color:#EEEEEE; } 9 | td { empty-cells:show; } 10 | td.t { font-family:Courier; font-size:85%; } 11 | td.k { font-family:Courier; font-size:85%; text-align:center; } 12 | a.ret { font-size:10px; } 13 | 14 | 15 | ul#index { 16 | list-style-type: none; 17 | list-style-position: outside; 18 | margin: 0 0 0 0; 19 | padding: 0 0 0 0; 20 | } 21 | 22 | ul#index li { 23 | background-color: #000000; 24 | margin: 8px 0 16px 0; 25 | border: 1px solid #000000; 26 | text-align: center; 27 | color: #FFFFFF; 28 | } 29 | 30 | ul#index li ul { 31 | list-style-type: none; 32 | margin: 0 0 0 0; 33 | padding: 0 0 0 0; 34 | } 35 | 36 | ul#index li ul li { 37 | background-color: #E8E8EF; 38 | margin: 0 0 0 0; 39 | padding: 5px 5px 5px 5px; 40 | border: none; 41 | text-align: left; 42 | text-decoration: underline; 43 | color: #000000; 44 | } 45 | 46 | ul#index li ul li ul { 47 | list-style-type: disc; 48 | list-style-position: inside; 49 | margin: 0 0 0 32px; 50 | padding: 0 0 0 0; 51 | } 52 | 53 | ul#index li ul li ul li { 54 | margin: 0 0 0 0; 55 | padding: 0 0 0 0; 56 | text-decoration: none; 57 | } 58 | -------------------------------------------------------------------------------- /client/.links: -------------------------------------------------------------------------------- 1 | IRCX/docbook/ http://chatzilla.rdmsoft.com/docs/ircx/docbook/ 2 | RPL_ISUPPORT/irc.org-tech_docs-005.html http://www.irc.org/tech_docs/005.html 3 | ctcp-1997.html http://www.invlogic.com/irc/ctcp.html 4 | ctcp-wboard.html http://www.visualirc.net/tech-wboard.php 5 | ctcp.html http://www.irchelp.org/irchelp/rfc/ctcpspec.html 6 | ctcp.txt https://www.alien.net.au/irc/ctcp.txt 7 | ctcp2.html http://www.invlogic.com/irc/ctcp2_intro.html 8 | ctcp2_1.html http://www.invlogic.com/irc/ctcp2_1.html 9 | ctcp2_2.html http://www.invlogic.com/irc/ctcp2_2.html 10 | ctcp2_3.html http://www.invlogic.com/irc/ctcp2_3.html 11 | ctcp2_4.html http://www.invlogic.com/irc/ctcp2_4.html 12 | ctcp2_5.html http://www.invlogic.com/irc/ctcp2_5.html 13 | ctcp2_6.html http://www.invlogic.com/irc/ctcp2_6.html 14 | ctcp2_intro.html http://www.invlogic.com/irc/ctcp2_intro.html 15 | dcc-reverse.txt http://cvs.epicsol.org/cgi/viewcvs.cgi/epic5/doc/DCC_REVERSE?rev=1.4 16 | dcc-turbo.html http://www.visualirc.net/tech-tdcc.php 17 | epic5-colors1.txt http://cvs.epicsol.org/cgi/viewcvs.cgi/epic5/doc/color.txt?rev=1.1.1.1 18 | epic5-colors2.txt http://cvs.epicsol.org/cgi/viewcvs.cgi/epic5/doc/colors?rev=1.1.1.1 19 | modeg.hybrid.txt svn://svn.ircd-hybrid.org/svnroot/ircd-hybrid/trunk/doc/modeg.txt 20 | troy-dcc.html http://www.irchelp.org/irchelp/rfc/dccspec.html 21 | xdcc-3.3.0b.irc http://xa.bi/files/irc/xdcc.3.3.0b.irc 22 | -------------------------------------------------------------------------------- /client/CAP-drafts/README: -------------------------------------------------------------------------------- 1 | Current specification is part of IRCv3 as "capability-negotiation-3.1" 2 | -------------------------------------------------------------------------------- /client/CTCP/ctcp2_6.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://www.invlogic.com/irc/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/CTCP/ctcp2_intro.html: -------------------------------------------------------------------------------- 1 | 2 | Internet Relay Chat 3 | 5 | 10 | 11 | 12 | 13 | 14 | 15 |

CTCP/2 - IRC client to client protocol

16 | This page contains information and links about CTCP/2, a protocol being 17 | crafted for IRC clients. It updates the rapidly aging CTCP specification, 18 | formalizes some features are current de-facto standards, and adds some 19 | interesting new things. 20 |

21 | The best way to find out about CTCP/2 is to read our draft. The draft is 22 | still being changed and discussed, so the documents here may change often. 23 |

24 |

CTCP Draft 25 | (last updated 28 oct 1997) 26 |

27 |
    28 |
  1. Introduction 29 |
    (reasonably up-to-date) 30 |
  2. Text Attributes 31 |
    (maybe finally put to rest?) 32 |
  3. Parsing CTCP Messages 33 |
    (finished but not voted on) 34 |
  4. CTCP Requests and Replies 35 |
    (finished but not voted on) 36 |
  5. DCC Requests 37 |
    (very much in flux) 38 |
  6. Appendices 39 |
    (reasonably up-to-date; based on other sections) 40 |
41 |

Status

42 | Section 2 has been updated to change the way on/off attributes are 43 | encoded. Hopefully that means sections 2, 3, and 4 are now effectively 44 | finished. Section 5 (DCC) still needs a lot more work. 45 |

46 |

Join the Discussion

47 | Our mailing list has moved! Lindsay's machine finally revolted against the 48 | load we were placing on it, so the list has moved to 49 | the-project.org. 50 |

51 | To subscribe: 52 | Send email to 53 | ctcp-request (at) the-project.org 54 | with the subject "subscribe". 55 |
56 | To read the archives: 57 | Check out 58 | http://www.the-project.org/ctcp/ 59 |

Demos

60 | This section will probably be very small until the draft achieves some 61 | stability. 62 |

63 | There is a small 64 | Java demo app (please read the 65 | README file first) 66 | which demonstrates what CTCP text attributes (section 2) will behave like. 67 | This was updated in October 1997 to reflect recent changes in that part of 68 | the draft (so check it out!). 69 |

70 | 71 | Maintained by: Webmaster, Innovative Logic Corp..
72 | Last modified: 17-Sep-2004 01:04PM.
73 |
74 | 75 | 76 | -------------------------------------------------------------------------------- /client/IRCX/docbook/apa.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/apa.html -------------------------------------------------------------------------------- /client/IRCX/docbook/apas02.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |

45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/apas03.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/apas03.html -------------------------------------------------------------------------------- /client/IRCX/docbook/apas04.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/apas04.html -------------------------------------------------------------------------------- /client/IRCX/docbook/apas05.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/apas05.html -------------------------------------------------------------------------------- /client/IRCX/docbook/apas06.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/apas07.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/apas08.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/apas09.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/apas10.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/apas11.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/apas12.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/ch01.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch01.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch02.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch02.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch02s02.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch02s02.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s02.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s02.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s03.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s03.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s04.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s04.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s05.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s05.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s06.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s06.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s07.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s07.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s08.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s08.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s09.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s09.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s10.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s10.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s11.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s11.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s12.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s12.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch03s13.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch03s13.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch04.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch04.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch04s02.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch04s02.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch04s03.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch04s03.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch04s04.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch04s04.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch04s05.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch04s05.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch04s06.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch04s06.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch04s07.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch04s07.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch04s08.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch04s08.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch05.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch05.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch05s02.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch05s02.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch06.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch06.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch06s02.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch06s02.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch07.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch07.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch07s02.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/ch07s02.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ch08.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/ch09.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/ch10.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/ch11.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | Internet Archive Wayback Machine 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 |
45 |
46 | 49 |
50 |
51 |
52 |
53 | 54 | 55 | 56 |
57 |
58 |
59 |
60 |
61 | 62 |

Hrm.

63 |

Wayback Machine doesn't have that page archived. It doesn't seem to be available on the live web, either.

64 | 65 |

Want to search for all archived pages under http://static.ignition-project.com/ircxdraft/ ?

66 | 67 | 68 |
69 |
70 |
71 | 72 | 73 | 74 | 75 | 76 | 77 |
84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /client/IRCX/docbook/index.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/index.html -------------------------------------------------------------------------------- /client/IRCX/docbook/ircx-draft.css: -------------------------------------------------------------------------------- 1 | body { 2 | font-family: Tahoma, Verdana, Helvetica, Arial, sans-serif; 3 | } 4 | 5 | td { 6 | padding: 5px; 7 | } 8 | 9 | th { 10 | padding: 5px; 11 | font-weight: bold; 12 | } 13 | 14 | .command { 15 | font-family: Courier New, monospace; 16 | font-weight: normal; 17 | font-size: 95%; 18 | } 19 | 20 | .synopsis { 21 | font-family: Courier New, monospace; 22 | font-weight: normal; 23 | font-size: 100%; 24 | } 25 | 26 | .note { 27 | padding: 10px; 28 | margin-top: 10px; 29 | border: 1px dashed #CCCCCC; 30 | } 31 | 32 | .token { 33 | font-weight: bold; 34 | font-size: 100%; 35 | border-left: 1px solid #FFFFFF; 36 | border-top: 1px solid #FFFFFF; 37 | border-bottom: 1px solid #999999; 38 | border-right: 1px solid #999999; 39 | background-color: #E6E6E6; 40 | color: #000000; 41 | padding: 0.12em; 42 | margin: 1px; 43 | vertical-align: middle; 44 | display: inline; 45 | margin-bottom: 10px; 46 | margin-top: 10px; 47 | line-height: 170%; 48 | } -------------------------------------------------------------------------------- /client/IRCX/docbook/pr01.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/pr01.html -------------------------------------------------------------------------------- /client/IRCX/docbook/pr02.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/pr02.html -------------------------------------------------------------------------------- /client/IRCX/docbook/pr03.html: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/client/IRCX/docbook/pr03.html -------------------------------------------------------------------------------- /client/IRCplus/.links: -------------------------------------------------------------------------------- 1 | psyc.eu-IRCPLUS.html https://web.archive.org/web/20100414055451/http://about.psyc.eu/IRCPLUS 2 | -------------------------------------------------------------------------------- /client/IRCplus/irc-plus/.links: -------------------------------------------------------------------------------- 1 | subscriptions-draft.html https://web.archive.org/web/20090629053420/http://www.irc-plus.org/specs/subscriptions-draft.html 2 | specs.html https://web.archive.org/web/20100529074640/http://www.irc-plus.org/specs/ 3 | identity-draft.html https://web.archive.org/web/20100428064456/http://www.irc-plus.org/specs/identity-draft.html 4 | index.html https://web.archive.org/web/20100529074640/http://www.irc-plus.org/en/ 5 | confctrl-draft.html https://web.archive.org/web/20081119144448/http://www.irc-plus.org/specs/confctrl-draft.html 6 | -------------------------------------------------------------------------------- /client/IRCplus/irc-plus/main.css: -------------------------------------------------------------------------------- 1 | body, 2 | html { 3 | margin:0; 4 | padding:0; 5 | } 6 | 7 | body{ 8 | font: 12px verdana; 9 | } 10 | 11 | a {color: #2153B0;} /* blue */ 12 | a:hover {color: #173A7B;} /* dark blue */ 13 | a:visited {color: green;} /* green */ 14 | 15 | #wrap { 16 | margin:0 auto; 17 | width:100%; 18 | } 19 | #header { 20 | } 21 | #header h1 { 22 | padding:5px; 23 | margin:0; 24 | } 25 | img { 26 | border:0; 27 | } 28 | 29 | #nav { 30 | padding:5px; 31 | border-top:black 1px dashed; 32 | border-bottom:black 1px dashed; 33 | } 34 | #nav ul{ 35 | margin:0; 36 | padding:0; 37 | list-style:none; 38 | display:inline; 39 | } 40 | #nav li{ 41 | display:inline; 42 | margin:0; 43 | padding:0; 44 | } 45 | #main { 46 | float:right; 47 | width:80%; 48 | } 49 | #main h2, #main h3, #main p { 50 | padding:0 10px; 51 | } 52 | #sidebar { 53 | float:right; 54 | width:19%; 55 | } 56 | #sidebar ul { 57 | margin-bottom:0; 58 | } 59 | #sidebar h5, #sidebar p { 60 | padding:0 10px 0 0; 61 | } 62 | #footer { 63 | clear:both; 64 | border-top:black 1px dashed; 65 | border-bottom:black 1px dashed; 66 | } 67 | #footer p { 68 | text-align: center; 69 | padding:5px; 70 | margin:0; 71 | } -------------------------------------------------------------------------------- /client/IRCplus/irc-plus/specs.html: -------------------------------------------------------------------------------- 1 | 19 | 20 | IRC+ Drafts 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 |
SIZEFILE
62673confctrl-draft.html
42254confctrl-draft.xml
73666identity-draft.html
57355identity-draft.xml
30864subscriptions-draft.html
12190subscriptions-draft.xml
53 | 54 |
55 | 
56 | 
57 | 
58 | This stuff isn't done yet.
59 | 
60 | While going through the interfaces of over a dozen
61 | services implementations I have understood that we
62 | can make a meta-specification which allows each of
63 | them to keep their own IRC services culture, yet at
64 | the same time provide a well-defined interface to
65 | the client developers.
66 | 
67 | This means adding some negotation options and
68 | general flexibility.
69 | 
70 | To get a better view of the work in progress, please look at
71 | 1. my irc+ wiki page
72 | 2. the comments embedded in the XML files.
73 | 
74 | Rock'n'roll --lynX
75 | 
76 | 77 | 78 | -------------------------------------------------------------------------------- /client/SASL/DH-AES.md: -------------------------------------------------------------------------------- 1 | --- 2 | status: obsolete 3 | --- 4 | 5 | # SASL DH-AES authentication mechanism 6 | 7 | © 2013–2015 Mantas Mikulėnas 8 | 9 | This specification documents the `DH-AES` SASL mechanism currently implemented 10 | by some IRC clients and services. 11 | 12 | The mechanism is non-standard, and specific to IRC software. It uses 13 | Diffie-Hellman key exchange to choose a shared encryption key, which is then 14 | used to encrypt the password sent to the server. 15 | 16 | The mechanism does not authenticate the server, and is considered insecure 17 | against active MITM attacks. Therefore it may give a false sense of security to 18 | users. It does however have improvements over DH-BLOWFISH. 19 | 20 | The mechanism does not allow an authorization identity to be specified. 21 | 22 | ## Step 1 23 | 24 | The server starts by sending a challenge containing the DH parameters _p_, _g_, 25 | and the server's public key, each serialized as two bytes containing the 26 | parameter's length (network byte order), followed by the parameter itself as an 27 | OpenSSL bignum. 28 | 29 | message = bignum(p) . bignum(g) . bignum(pub_key) 30 | 31 | ## Step 2 32 | 33 | The client computes the shared key from the received DH parameters, and uses it 34 | to encrypt the credentials using AES-128 in CBC mode with a random IV. 35 | 36 | The credentials consist of username (authentication identity) and password 37 | concatenated together; each item must be encoded as UTF-8 and null-terminated. 38 | The result is then padded to 16 bytes. 39 | 40 | The client then sends the response consisting of its own DH public key, the IV, 41 | and the encrypted credentials. Again, the public key is serialized as two bytes 42 | containing the length, followed by the key itself as a bignum. 43 | 44 | raw_credentials = pad(16, cstring(authn_id) . cstring(password)) 45 | 46 | enc_credentials = aes128_cbc[shared_key, iv](raw_credentials) 47 | 48 | message = bignum(pub_key) . iv . enc_credentials 49 | 50 | ## Step 3 51 | 52 | The server computes the same shared key from the DH parameters and client's 53 | public key, and uses it to decrypt the username and password. 54 | -------------------------------------------------------------------------------- /client/SASL/DH-BLOWFISH.md: -------------------------------------------------------------------------------- 1 | --- 2 | status: obsolete 3 | --- 4 | 5 | # SASL DH-BLOWFISH authentication mechanism 6 | 7 | © 2013–2015 Mantas Mikulėnas 8 | 9 | This specification documents the `DH-BLOWFISH` SASL mechanism currently 10 | implemented by various IRC clients and services. 11 | 12 | The mechanism is non-standard, and specific to IRC software. It uses 13 | Diffie-Hellman key exchange to choose a shared encryption key, which is then 14 | used to encrypt the password sent to the server. 15 | 16 | The mechanism does not authenticate the server, and is considered insecure 17 | against active MITM attacks. 18 | 19 | The mechanism does not allow an authorization identity to be specified. 20 | 21 | The mechanism is considered deprecated and should be avoided, as it gives a 22 | false sense of security to many users. 23 | 24 | ## Step 1 25 | 26 | The server starts by sending a challenge containing the DH parameters _p_, _g_, 27 | and the server's public key, each serialized as two bytes containing the 28 | parameter's length (network byte order), followed by the parameter itself as an 29 | OpenSSL bignum. 30 | 31 | message = bignum(p) . bignum(g) . bignum(pub_key) 32 | 33 | ## Step 2 34 | 35 | The client computes the shared key from the received DH parameters, and uses it 36 | to encrypt the password using Blowfish in ECB mode. The password must be 37 | encoded as UTF-8 and null-terminated. 38 | 39 | The client then sends the response consisting of its own DH public key, the 40 | authentication identity as a null-terminated string, and the encrypted 41 | password. Again, the public key is serialized as two bytes containing the 42 | length, followed by the key itself as a bignum. 43 | 44 | raw_credentials = pad(8, cstring(password)) 45 | 46 | enc_credentials = blowfish_ecb[shared_key](raw_credentials) 47 | 48 | message = bignum(pub_key) . cstring(authn_id) . enc_credentials 49 | 50 | ## Step 3 51 | 52 | The server computes the same shared key from the DH parameters and client's 53 | public key, and uses it to decrypt the password. 54 | -------------------------------------------------------------------------------- /client/SOURCE: -------------------------------------------------------------------------------- 1 | modeg.hybrid.txt svn://svn.ircd-hybrid.org/svnroot/ircd-hybrid/trunk/doc/modeg.txt 2 | -------------------------------------------------------------------------------- /client/cap-identify-msg.md: -------------------------------------------------------------------------------- 1 | # identify-msg Client Capability Extension 2 | 3 | The `identify-msg` capability causes the server to send an "identification" 4 | prefix in the message parameter of PRIVMSG and NOTICES commands. 5 | 6 | The prefix is a single character, `+` (ASCII plus) if the sender is 7 | "identified" according to services, `-` (ASCII minus) otherwise. 8 | 9 | The definition of 'identified' varies between services software. For example: 10 | 11 | - "has the +r usermode set" – if services dynamically set/unset the umode; 12 | - "is identified to an account which owns the current nickname" – if services 13 | provide such information in other ways; 14 | - "is identified to any account" – if services don't implement nickname 15 | ownership at all. 16 | 17 | For this reason, the extension must not be used for security purposes. 18 | 19 | Example (demonstrated using the `account-notify` capability): 20 | 21 | :user ACCOUNT * 22 | :user PRIVMSG #atheme :-Hello everyone. 23 | :user ACCOUNT user 24 | :user PRIVMSG #atheme :+Now I'm logged in. 25 | :user NICK loser 26 | :loser PRIVMSG #atheme :-I'm still logged in, but my account does not match. 27 | 28 | Historical note: There exist pre-IRCv3 servers and clients that implement the 29 | same extension as `CAPAB IDENTIFY-MSG`. New servers and clients SHOULD NOT 30 | implement the CAPAB command. 31 | 32 | In fact, this extension is entirely superseded by the newer capabilities 33 | `account-msg`, `account-notify`, and `extended-join`, which also allow for 34 | services implementations that have account names different from nicknames. The 35 | `identify-msg` extension therefore should not be implemented. 36 | -------------------------------------------------------------------------------- /client/epic5-colors1.txt: -------------------------------------------------------------------------------- 1 | About Control-C colors 2 | 3 | If your client was compiled with #define CONTROL_C_COLORS and you have 4 | /SET CONTROL_C_COLORS ON, then you can use the control-c colors feature. 5 | The general syntax is: 6 | 7 | color-seq-start := "^C" [number] ["," number] 8 | color-seq-end := "^C" 9 | 10 | The first "number" is a positive integer at least 0 and not more than 15. 11 | The colors correspond to the ANSI color schema: 12 | 13 | 0 - black 1 - red 2 - green 3 - yellow 14 | 4 - blue 5 - magenta 6 - cyan 7 - white 15 | 16 | The colors 8 through 15 are the corresponding "bold" versions of the colors 17 | above, whatever that may be for your terminal. 18 | 19 | The "standard" as imposed by mIRC forbids an empty leading value. This 20 | implementation choses not to impose this draconian restriction. So there. 21 | 22 | If you wish to defeat the color codes, you can have them filtered out by 23 | doing /SET CONTROL_C_COLORS OFF. 24 | 25 | 26 | OUR REVISIONS TO THE "STANDARD": 27 | 28 | The syntax of colors has been modified to: 29 | 30 | color-seq-start := "\003" + color-term + ["," color-term] 31 | color-term := ["0" + ["0..9"] | "1" + ["0..5"] ] | ["2..9"] | [""] 32 | color-seq-end := "\003" 33 | 34 | Specifically, this implementation guarantees that at least zero and at most 35 | two character will ever be used to construct the color code. If the first 36 | character is a 0, then the second character will be used if it is a number. 37 | If the first character is a 1, then the second character will be used only if 38 | it is a number at least 0 and at most 5. A comma following the first color 39 | term will only be "eaten" if it is followed by another valid term. 40 | 41 | Either the first term or the second term may be empty. If either term (but 42 | not both) are ommitted, then no change will occur for that modifier. If both 43 | terms are omitted, the comma must also be omitted, and all color attributes 44 | will be terminated. 45 | 46 | It is hoped that this clarification will allow the deterministic use of color 47 | codes (if you always use two digit codes, then you will never have a problem 48 | with the color codes munching too many characters.) 49 | 50 | -end of file- 51 | 52 | 53 | 0 -> white 1-> black 2-> blue 3-> green 4-> red 54 | -------------------------------------------------------------------------------- /misc-notes.txt: -------------------------------------------------------------------------------- 1 | # On the meaning of "TS6ow" 2 | 3 | jilles: I'm curious what "ow" means in the "TS:ow" or "TS6ow" 4 | in the version strings 5 | <@jilles> grawity, pretty much obsolete -- o = TS only, w = TS warnings 6 | (when a non-TS server is connected remotely) 7 | <@jilles> the warnings are long gone but the 'w' has stayed 8 | 9 | (staticbox.#charybdis @ 2013-04-03 17:52 +0300) 10 | 11 | # On the meaning of "TS3ora" 12 | 13 | relaative chans was roger's earlier proposal that was never 14 | fully built 15 | RogerY as in author of OPAS and Austhex? 16 | vchans was the actual implementation of relative chans, but 17 | relative chans was envisioned to have servcerside ignore emulating 18 | channel modes. 19 | no, roger as in TS3ora 20 | Efnet's original TS implementation IIRC 21 | roger espel llima I think 22 | aha, yes 23 | well, the 'ora' comes from orabidoo 24 | 25 | ("orabidoo" appears to be Roger Espel Llima's nickname) 26 | 27 | (staticbox.#ircv3 @ 2013-02-26 18:14 +0200) 28 | 29 | # On "login on connect" 30 | 31 | (Jobe) well with SASL the idea is to phase LOC out as the preferred anyway 32 | (Jobe) doc/readme.login-on-connect is out of date anyway 33 | (Jobe) the current syntax for PASS when using LOC is "PASS [ ][[[/]/]/] 34 | -------------------------------------------------------------------------------- /misc/PTlink-vlinks.txt: -------------------------------------------------------------------------------- 1 | Virtual Links 2 | - - - - - - - - 3 | Originally implemented at Brasnet by fabulous@t7ds.com.br 4 | - - - - - - - - 5 | Virtual links allow to setup virtual server names. 6 | Virtual server names will allow to fake various irc servers from the same 7 | irc net running on the same host/port depending on the client's 8 | connection request. 9 | This is done by looking into the server name field sent by the client 10 | during on connection USER message. If the server name matches an 11 | existing virtual link, all messages sent to that client will look like 12 | originating from the virtual server. 13 | Note that its a single ircd process handling connections at a common 14 | host/port 15 | 16 | Commands covered by vlinks: 17 | VERSION* 18 | WHO* 19 | WHOIS* 20 | NAMES* 21 | MODE* 22 | MOTD* 23 | HELPSYS* 24 | NEWMASK* 25 | LINKS* 26 | STATS* 27 | * = done 28 | -------------------------------------------------------------------------------- /misc/SOURCE: -------------------------------------------------------------------------------- 1 | atheme-plus.html http://rabbit.dereferenced.org/~nenolod/atheme-plus.html 2 | kalt-irc/channel.html https://web.archive.org/web/20020203231521/http://www.stealth.net/~kalt/irc/channel.html 3 | kalt-irc/collisions.html https://web.archive.org/web/20020606022119/http://www.stealth.net/~kalt/irc/stats/collisions.html 4 | kalt-irc/faq.html https://web.archive.org/web/20020408131601/http://www.stealth.net/~kalt/irc/faq.html 5 | kalt-irc/index.html https://web.archive.org/web/20020205124254/http://www.stealth.net/~kalt/irc/ 6 | kalt-irc/kills.html https://web.archive.org/web/20020202201256/http://www.stealth.net/~kalt/irc/kills.html 7 | kalt-irc/TS-Delay.html https://web.archive.org/web/20020202193627/http://www.stealth.net/~kalt/irc/TS-Delay.html 8 | ora-relative-chanops.txt ftp://quatramaran.ens.fr/pub/orabidoo/relative-chanops 9 | 10 | freenode-2006/BreakageSlash.html http://web.archive.org/web/20051216015324/http://partiallystapled.com/wiki/index.php/BreakageSlash 11 | freenode-2006/FreenodeRegistryDiscussions.html http://web.archive.org/web/20051216011112/http://partiallystapled.com/wiki/index.php/FreenodeRegistryDiscussions 12 | freenode-2006/Freenode_Registry.html http://web.archive.org/web/20051216015050/http://partiallystapled.com/wiki/index.php/Freenode_Registry 13 | freenode-2006/HyperionNOIDPREFIX.html http://web.archive.org/web/20051030210406id_/http://partiallystapled.com/wiki/index.php/HyperionNOIDPREFIX 14 | freenode-2006/HyperionNOIDPREFIXPurpose.html http://web.archive.org/web/20051212122006/http://partiallystapled.com/wiki/index.php/HyperionNOIDPREFIXPurpose 15 | freenode-2006/Talk:HyperionNOIDPREFIXPurpose.html http://web.archive.org/web/20051216001554/http://partiallystapled.com/wiki/index.php/Talk:HyperionNOIDPREFIXPurpose 16 | freenode-2006/TraditionalIRCUsers.html http://web.archive.org/web/20051216015351/http://partiallystapled.com/wiki/index.php/TraditionalIRCUsers 17 | -------------------------------------------------------------------------------- /misc/bahamut-server-version-info.txt: -------------------------------------------------------------------------------- 1 | When you type /version you will often see something like this: 2 | bahamut-1.8(02). server aABCdFhistTY/HoS TS5ow-r[RELEASE] RPL1 NP[U] 3 | 4 | Ever wondered what those funny chars mean after the version number? Well 5 | here they are: 6 | 7 | The first set before the '/' are compile-time flags: 8 | 'a' config.h ANTI_SPAMBOT 9 | 'A' config.h ALWAYS_SEND_DURING_SPLIT 10 | 'B' config.h MAXBUFFERS 11 | 'C' config.h CMDLINE_CONFIG 12 | 'd' config.h DO_IDENTD 13 | 'D' config.h DEBUGMODE 14 | 'E' configure encryption support enabled 15 | 'F' config.h FLUD 16 | 'h' config.h SHOW_HEADERS 17 | 'i' config.h SHOW_INVISIBLE_LUSERS 18 | 'I' config.h NO_DEFAULT_INVISIBLE 19 | 'J' config.h NO_DEFAULT_JOINRATE 20 | 'M' configure module support enabled 21 | 'N' config.h DNS_DEBUG 22 | 'r' config.h DENY_SERVICES_MSGS 23 | 's' config.h SUPER_TARGETS_ONLY 24 | 't' config.h MSG_TARGET_LIMIT 25 | 'T' config.h THROTTLE_ENABLE 26 | 'u' config.h IRCII_KLUDGE 27 | 'Y' config.h USE_SYSLOG 28 | 29 | The first set after the '/' are runtime flags: 30 | 'H' ircd.conf servtype = hub 31 | 'm' ircd.conf short_motd 32 | 'o' ircd.conf allow_split_ops 33 | 'p' ircd.conf crypt_oper_pass 34 | 'S' ircd.conf servtype = serviceshub 35 | 'w' ircd.conf wgmonhost/wgmonurl 36 | 37 | The next part, 'TS5ow', is mostly historical. The release tag is provided 38 | after it. 39 | 40 | If 'RPL#' shows up, oper hostmasking is enabled. The number is the level: 41 | 1 All +A users can see real IP 42 | 2 Local +A users can see real IP 43 | 3 Noone can see real IP (but it's still logged) 44 | 45 | The last part, 'NP[]', contains network information hiding flags: 46 | 'A' config.h FORCE_EVERYONE_HIDDEN 47 | 'I' config.h ALLOW_HIDDEN_OPERS 48 | 'K' config.h HIDE_KILL_ORIGINS 49 | 'L' ircd.conf no show_links (hiding LINKS) 50 | 'M' config.h HIDE_SERVERMODE_ORIGINS 51 | 'N' config.h HIDE_NUMERIC_SOURCE 52 | 'O' config.h NO_USER_OPERTARGETED_COMMANDS 53 | 'P' config.h HIDE_SPLIT_SERVERS 54 | 'S' config.h NO_USER_STATS 55 | 'T' config.h NO_USER_TRACE 56 | 'U' config.h HIDEULINEDSERVS 57 | 'W' config.h NO_USER_SERVERNOTICES 58 | -------------------------------------------------------------------------------- /misc/bitnet/SOURCE: -------------------------------------------------------------------------------- 1 | relay-faq.html http://web.inter.nl.net/users/fred/relay/faq.html 2 | relay-history.html http://web.inter.nl.net/users/fred/relay/relhis.html 3 | relay-info.html http://web.inter.nl.net/users/fred/relay/relinf.html 4 | relay-rules.html http://web.inter.nl.net/users/fred/relay/relrul.html 5 | relay-smart_vmcms-commands.html http://web.inter.nl.net/users/fred/relay/smari.html 6 | relay-smart_vmcms-hints.html http://web.inter.nl.net/users/fred/relay/smarh.html 7 | relay-usage.html http://web.inter.nl.net/users/fred/relay/reluse.html 8 | relay-xyzzy_vms-help.html http://web.inter.nl.net/users/fred/relay/xyzzy.html 9 | relay-chat_vmcms-help.html http://web.inter.nl.net/users/fred/relay/chath.html 10 | -------------------------------------------------------------------------------- /misc/bitnet/relay-rules.html: -------------------------------------------------------------------------------- 1 | 2 | Relay Rules and Guidelines 3 | 4 |

Relay Rules and Guidelines

5 |
6 | (User Responsibilities Section excerpted from RELAY INFO file.) 7 |

8 | Relay is a distributed message server which, by selective switching and 9 | redistribution of messages, provides real-time conferencing capabilities 10 | while minimizing the overhead on the network links. Since the potential 11 | load of uncontrolled message traffic on the network can affect transfer 12 | of files, stringent controls over Relay use are mandatory. Most control 13 | measures are enforced by Relay automatically, but some are necessarily 14 | the responsibility of the user. These include: 15 |

16 |

    17 |
  • 18 | Each Relay server provides service to a specific collection of 19 | one or more nodes designated as a "service area". You should 20 | direct your queries only to your assigned Relay. 21 | 22 |
  • 23 | Excessive queries, channel changes, nick changes, and other 24 | commands which must be processed by Relay generate considerable 25 | overhead and should be kept to a minimum. 26 | 27 |
  • 28 | File backlogs, Relay host CPU saturation, link failures, and node 29 | downtime may make Relay temporarily unavailable or restricted. 30 | 31 |
  • Proper and considerate behavior should be observed at all times. 32 | The same socially accepted behavior in public in real life also 33 | applies to your conduct and behavior on Relay. Behavior on 34 | public channels (0-99) should follow conservative standards. Less 35 | restrictive standards can be followed on private channels (100-999). 36 | 37 |

    Some DON'TS in the behavior category include, but are not limited 38 | to, the following: 39 |

    40 |

      41 |
    • Disguising your identity in a /REGister (or /SIGNUP) by not 42 | specifying your full name or by specifying someone else's name. 43 |
    • Transmitting rude or obscene language. 44 |
    • Using obscene or offensive nicks; using all-symbol nicks. 45 |
    • Signing-on more than one account on Relay at the same time. 46 |
    • Channel scanning; attempting to intrude on a private channel 47 | without obtaining an invitation from a user on that channel. 48 |
    • Annoying other Relay users by transmitting excessive and/or 49 | repetitive messages (including pictures). 50 |
    • Failing to cease an activity in response to a request to do so 51 | from any individual designated as a 'Relay Operator'. 52 |
    • Rude and discourteous behavior toward other users. The same 53 | manners and courtesies that apply to every day life also 54 | apply to Relay. 55 |
    • Using other people's accounts without their permission and 56 | without the node admin's permission. Using other people's 57 | accounts for Relaying without the Masterop's approval. 58 |
    • Running programs on Relay without prior permission from 59 | the MasterOp and/or node admin; signed onto Relay disconnected; 60 | (loads the net and raises cpu unnecessarily). 61 |

    62 | 63 |

  • Abusive and obscene behavior should be reported to a RelayOp 64 | who is signed onto Relay at that time by issuing the "/GETOP" 65 | command. (This command shouldn't be used for trivial or 66 | non-Relay matters, however.) If you get no response from the 67 | "/GETOP" command, you can send a note about the problem to 68 | your Master RelayOp. (Sending the "/CO" command to your Relay 69 | will give you your Relay's MasterOp's name and userid.) 70 |

71 | Not observing Relay and Bitnet guidelines and protocol can result in 72 | suspension of Relay privileges. Relay is a *privilege*, NOT a right, 73 | and Relay abuse will NOT be tolerated! 74 |

75 |


76 | 77 | 78 | -------------------------------------------------------------------------------- /misc/hybrid-server-version-info.txt: -------------------------------------------------------------------------------- 1 | $Id: server-version-info,v 1.3 2005/08/27 16:23:49 jpinto Exp $ 2 | Updated for Hybrid 6 (2000/11/26) 3 | 4 | When you type /version you will often see something like this: 5 | *** 2.8/hybrid-6rc6(20001110_1). irc.ins.net.uk ACHiIMpY TS3ow 6 | 7 | Ever wondered what those funny chars mean after the version number? Well 8 | here they are: 9 | 10 | 'A' SENDQ_ALWAYS 11 | 'C' CMDLINE_CONFIG 12 | 'D' DEBUGMODE 13 | 'e' CHANMODE_E 14 | 'g' NO_FAKE_GLINES 15 | 'G' GLINES 16 | 'H' HUB 17 | 'i' SHOW_INVISIBLE_LUSERS 18 | 'K' USE_KNOCK 19 | 'M' IDLE_FROM_MSG 20 | 'p' CRYPT_OPER_PASSWORD 21 | 'P' CRYPT_LINK_PASSWORD 22 | 'T' IGNORE_BOGUS_TS 23 | 'Y' USE_SYSLOG 24 | 'Z' ZIP_LINKS 25 | 26 | 'TS' Supports TS 27 | '3' TS Version 3 (Gives ops on splits, on opless channels) 28 | '5' TS Version 5 (Impossible to gain ops after a netsplit) 29 | 'o' TS Only 30 | 'w' TS Warnings 31 | 'c' TS Current and higher only. 32 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/00changelog.i: -------------------------------------------------------------------------------- 1 |  dummy changelog to prevent using the old repo layout -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/branch: -------------------------------------------------------------------------------- 1 | irc-documentation 2 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/cache/branchheads: -------------------------------------------------------------------------------- 1 | 54870aec98e4e48a50e84014f8a6977ecfe19ec6 105 2 | 54870aec98e4e48a50e84014f8a6977ecfe19ec6 irc-documentation 3 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/cache/tags: -------------------------------------------------------------------------------- 1 | 105 54870aec98e4e48a50e84014f8a6977ecfe19ec6 2 | 3 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/dirstate: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/dirstate -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/hgrc: -------------------------------------------------------------------------------- 1 | [paths] 2 | default = http://www.stack.nl/~jilles/cgi-bin/hgwebdir.cgi/irc-documentation-jilles/ 3 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/requires: -------------------------------------------------------------------------------- 1 | revlogv1 2 | fncache 3 | store 4 | dotencode 5 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/00changelog.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/00changelog.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/00manifest.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/00manifest.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/architecture.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/architecture.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/channel management.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/channel management.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/client protocol.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/client protocol.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/1459.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/1459.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/2810.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/2810.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/2811.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/2811.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/2812.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/2812.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/2813.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/2813.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/draft-hardy-irc-isupport-00.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/draft-hardy-irc-isupport-00.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/draft-meglio-irc-handshake-00.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/draft-meglio-irc-handshake-00.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/draft-meglio-irc-watch-00.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/draft-meglio-irc-watch-00.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/draft-mitchell-irc-capabilities-02.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/draft-mitchell-irc-capabilities-02.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/modeg.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/modeg.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/monitor.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/monitor.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/data/reference/snomasks.txt.i: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/data/reference/snomasks.txt.i -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/fncache: -------------------------------------------------------------------------------- 1 | data/architecture.txt.i 2 | data/reference/draft-mitchell-irc-capabilities-02.txt.i 3 | data/reference/draft-meglio-irc-handshake-00.txt.i 4 | data/reference/2811.txt.i 5 | data/reference/2813.txt.i 6 | data/reference/snomasks.txt.i 7 | data/channel management.txt.i 8 | data/reference/draft-hardy-irc-isupport-00.txt.i 9 | data/reference/1459.txt.i 10 | data/reference/monitor.txt.i 11 | data/client protocol.txt.i 12 | data/reference/2812.txt.i 13 | data/reference/modeg.txt.i 14 | data/reference/draft-meglio-irc-watch-00.txt.i 15 | data/reference/2810.txt.i 16 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/phaseroots: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/phaseroots -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/undo: -------------------------------------------------------------------------------- 1 | 00changelog.i0 2 | 00manifest.i0 3 | data/architecture.txt.i0 4 | data/channel management.txt.i0 5 | data/client protocol.txt.i0 6 | data/reference/1459.txt.i0 7 | data/reference/2810.txt.i0 8 | data/reference/2811.txt.i0 9 | data/reference/2812.txt.i0 10 | data/reference/2813.txt.i0 11 | data/reference/draft-hardy-irc-isupport-00.txt.i0 12 | data/reference/draft-meglio-irc-handshake-00.txt.i0 13 | data/reference/draft-meglio-irc-watch-00.txt.i0 14 | data/reference/draft-mitchell-irc-capabilities-02.txt.i0 15 | data/reference/modeg.txt.i0 16 | data/reference/monitor.txt.i0 17 | data/reference/snomasks.txt.i0 18 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/store/undo.phaseroots: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/store/undo.phaseroots -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/undo.bookmarks: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/undo.bookmarks -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/undo.branch: -------------------------------------------------------------------------------- 1 | default -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/undo.desc: -------------------------------------------------------------------------------- 1 | 0 2 | pull 3 | http://www.stack.nl/~jilles/cgi-bin/hgwebdir.cgi/irc-documentation-jilles/ 4 | -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/.hg/undo.dirstate: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/irc-documentation-jilles/.hg/undo.dirstate -------------------------------------------------------------------------------- /misc/irc-documentation-jilles/reference/snomasks.txt: -------------------------------------------------------------------------------- 1 | jilles, how does hyperion do snomasks? 2 | it doesn't 3 | that and umodes-as-privs makes hyperion's umode system really enormous 4 | or are you actually asking about charybdis 5 | err 6 | yeah 7 | sorry, brainfreeze 8 | MODE +s (enables a default set, namely +s) 9 | patch committed 10 | MODE +s 11 | MODE -s (clear all) 12 | that's what the client can send 13 | +s -foo+bar? 14 | yeah 15 | snomask changes can be combined with other umodes 16 | i think we need to standardise on this system then 17 | afaik unreal's works the same way 18 | when sending it out to the client, charybdis will never use this syntax 19 | ours does too, except we currently use +n 20 | er. 21 | you don't send +s back? 22 | it sends +s without parameters, if it changed; then RPL_SNOMASK with the new snomask 23 | hmm. 24 | a little trippy 25 | RPL_SNOMASK is also send after RPL_UMODEIS if you MODE 26 | though 27 | that actually makes more sense in that perspective, yeah 28 | ircu works similarly, except that snomasks are decimal numbers there 29 | -------------------------------------------------------------------------------- /misc/kline.txt: -------------------------------------------------------------------------------- 1 | /* doc/kline.txt - Overview of the remote kline system 2 | * 3 | * Copyright (C) 2005 Hybrid Development Team 4 | * 5 | * $Id: kline.txt 410 2006-02-08 14:31:37Z michael $ 6 | */ 7 | 8 | 9 | Introduction 10 | ------------ 11 | 12 | ircd-hybrid-7 will allow opers to add and remove K-Lines on multiple servers, 13 | an extension and replacement of the old ircd-hybrid-6 method of sharing 14 | all K-Lines between servers. 15 | 16 | In this implementation, it is extended to be routable among servers which 17 | understand the "KLN" capability. This allows us to continue to "talk" 18 | to non remote kline capable servers without breaking anything. 19 | 20 | K-Lines have also received a new feature of supporting regular expressions 21 | to allow for more flexible bans. 22 | 23 | Usage 24 | ----- 25 | 26 | The old K-Line method has not been changed. To place a K-Line it is still: 27 | 28 | /quote kline :reason 29 | /quote kline [tkline_duration] :reason 30 | 31 | Scenario 1 32 | ---------- 33 | 34 | Oper wishes to K-Line user@host on server irc.xyz.net 35 | 36 | /quote kline on irc.xyz.net :reason 37 | /quote kline [duration] on irc.xyz.net :reason 38 | 39 | Scenario 2 40 | ---------- 41 | 42 | Oper wishes to K-Line user@host on all servers named *.uk 43 | 44 | /quote kline on *.uk :reason 45 | /quote kline [duration] on *.uk :reason 46 | 47 | Scenario 3 48 | ---------- 49 | 50 | Oper wishes to place a network wide K-Line on user@host 51 | 52 | /quote kline on * :reason 53 | /quote kline [duration] on * :reason 54 | 55 | Scenario 4 56 | ---------- 57 | 58 | Oper wishes to K-Line a flexible ban on various user@host types 59 | 60 | /quote rkline ^O[[:alpha:]]?[[:digit:]]+(x\.o|\.xo)$@^[[:alnum:]]{4}\.evilnet.org$ :reason 61 | 62 | Authorization 63 | ------------- 64 | 65 | For the K-Line to be accepted by the remote server, the server must have 66 | explicitly allowed K-Lines from that user. This is done via a shared {}; 67 | block in ircd.conf. 68 | 69 | The shared block contains two settings, a user@host mask of the oper 70 | who is allowed to K-Line, and a servername. 71 | 72 | - If both of these options are present, K-Lines will only be allowed 73 | from that specific user@host on that specific server. 74 | - If only the servername is present, all K-Lines from opers on that 75 | server will be accepted. 76 | - If only the user@host is present, all K-Lines from that user@host on 77 | any server will be accepted. 78 | - If neither are present, the shared block is invalid. 79 | 80 | shared { 81 | /* The name of the server we allow K-Lines from */ 82 | name = "this.server.net"; 83 | 84 | /* the user@host allowed to K-Line */ 85 | user = "user@host.com"; 86 | }; 87 | 88 | Server to Server Protocol 89 | ------------------------- 90 | 91 | As mentioned above, each server capable of remote K-Lines passes 92 | the capability KLN along. No server will send a KLINE to a server 93 | without a KLN capability. 94 | 95 | Server to server messages are formatted like this: 96 | 97 | ":oper KLINE target.server duration user host :reason" 98 | 99 | Note the difference between hybrid-6 GLINE which explicitly passed 100 | the oper user@host and server along. This was originally done to handle 101 | possible desync conditions, but is now shelved in favor of saving 102 | some bandwidth. 103 | 104 | oper: the nick of the oper performing the K-Line 105 | target.server: the server(s) this K-Line is destined for 106 | duration: the duration if a TK-Line, 0 if permanent. 107 | user: the 'user' portion of the K-Line 108 | host: the 'host' portion of the K-Line 109 | reason: the reason for the K-Line. 110 | -------------------------------------------------------------------------------- /misc/services.txt: -------------------------------------------------------------------------------- 1 | ratbox-services compatibility documentation - Lee H 2 | ------------------------------------------------------------------------- 3 | 4 | Compatibility with ratbox-services is always enabled. Note that some or 5 | all of this is also used by atheme-services and anope. It will add the 6 | following features to ircd: 7 | 8 | 1. Channel mode +r 9 | 10 | A simple mode taking no parameters, will require users are logged in 11 | with user services before they may join the channel. 12 | 13 | Gives numeric 477 to users who arent logged in: 14 | : 477 :Cannot join channel (+r) 15 | 16 | 2. service block to ircd.conf 17 | 18 | Ability to specify the names of services servers in ircd.conf: 19 | service { 20 | name = "services.ircd-ratbox.org"; 21 | name = "backup-services.ircd-ratbox.org"; 22 | }; 23 | 24 | These must be specified for certain features to work. You may specify as 25 | many name entries as you wish, however you must define only one service 26 | block. 27 | 28 | Entries will be listed in stats U with the flag 's'. 29 | 30 | 3. Services protection 31 | 32 | Services will be protected from being deopped or kicked from a channel. 33 | 34 | 4. Username tracking through netsplits 35 | 36 | When users are logged in, the username they are logged in with will be 37 | preserved on a netsplit, so users will not have to relogin when the 38 | network merges together. 39 | 40 | 5. Username given on WHOIS 41 | 42 | When users are logged in, WHOIS will also give numeric 330: 43 | : 330 :is logged in as 44 | 45 | 6. Forced nick change 46 | 47 | When using nickname services and a client requests they regain a 48 | nickname, services can perform a forced nick change on the client. 49 | This forcibly changes the clients nickname to the one they requested 50 | they regain, ensuring they can always regain their nickname. 51 | 52 | 7. User mode +R 53 | 54 | This user mode will require users are logged in with user services 55 | before they may send private messages or notices to the user. 56 | 57 | As with user mode +g, IRC operators and accepted users can send even 58 | if they are not logged in. 59 | 60 | Gives numeric 486 to users sending a PRIVMSG who are not logged in: 61 | : 486 :You must log in with services to message this user 62 | 63 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0001.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Final Voting Policies
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: riedel (efnet.vuurwerk.nl)
6 | Called on: 01/26/01
7 | Ended on: 02/09/01
8 | Status: PASSED (yes: 20, no: 0, abstain: 0, elig: ~25)

9 | 10 | Description:

11 | 12 |
13 | 
14 | 1) Definition of a majority vote
15 | 
16 | A vote will be considered "passed" if:
17 | 
18 | (number of yes votes) / (number of cast votes) >= 51%, provided that at least 51%
19 | of eligible servers cast a vote.
20 | 
21 | 2) Duration of vote process
22 | 
23 | Vote duration will be left up to the caller.  It is suggested that most votes be
24 | given 2 weeks to run their course.  In extreme cases where there is good reason to
25 | call a vote with a shorter duration, the 51% turnout requirement will still hold
26 | in order to reach a majority.
27 | 
28 | 3) Voter eligibility
29 | 
30 | It is up to each admin who may vote on behalf of their server.  Admins with more
31 | than one server may cast votes or elect persons to cast votes for each server
32 | provided that the servers are considered seperate entities by the admin community
33 | (i.e. irc.west.gblx.net and irc.east.gblx.net receive one vote, irc.total.net and
34 | irc.magic.ca receive two votes).
35 | 
36 | 
37 | Details:
38 | 
39 | irc.core.com: YES
40 | irc.emory.edu: YES
41 | irc.plur.net: YES
42 | irc.total.net: YES
43 | irc.lightning.net: YES
44 | irc.rt.ru: YES
45 | irc.umn.edu: YES
46 | irc.light.se: YES
47 | irc.colorado.edu: YES
48 | irc.du.se: YES
49 | irc.umich.edu: YES
50 | irc.hemmet.chalmers.se: YES
51 | irc2.magic.ca: YES
52 | efnet.vuurwerk.nl: YES
53 | irc.stanford.edu: YES
54 | irc.exodus.net: YES
55 | irc.ins.net.uk: YES
56 | irc.isdnet.fr: YES
57 | irc.gigabell.de: YES
58 | irc.prison.net: YES
59 | 
60 | 
61 | 62 |

63 | 64 | Click Here to go back.
65 | 66 | 67 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0002.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Addition to the voting policies
4 | Called by: riedel (efnet.vuurwerk.nl)
5 | Seconded by: Tsk (irc.lightning.net)
6 | Called on: 01/28/01
7 | Ended on: 02/12/01
8 | Status: PASSED (yes: 20, no: 0, abstain: 0, elig: ~25)

9 | 10 | Description:

11 | 12 |
13 | 
14 | 1) Votes cast will be collected by the voting admin(s) and
15 | made public after the vote period is over or a majority
16 | has been reached.
17 | 
18 | 2) Only a representative of a server that has acquired a
19 | permanent link to EFnet may vote on behalf of his/her server.
20 | 
21 | 3) A representative of a server cannot vote on issues that involve that admin
22 | and/or the server he/she represents directly.
23 | 
24 | 4) In case one admin represents multiple servers that can be
25 | seen as one, we (the admins) should discuss the number of
26 | votes that server gets. If there is failure to agree, it will be decided by vote.
27 | 
28 | 
29 | Details:
30 | 
31 | irc.rt.ru: YES
32 | irc2.magic.ca: YES
33 | irc.prison.net: YES
34 | irc.hemmet.chalmers.se: YES
35 | irc.ins.net.uk: YES
36 | irc.stanford.edu: YES
37 | irc.gigabell.de: YES
38 | irc.core.com: YES
39 | irc.umn.edu: YES
40 | irc.colorado.edu: YES
41 | irc.emory.edu: YES
42 | irc.total.net: YES
43 | irc.light.se: YES
44 | irc.du.se: YES
45 | irc.concentric.net: YES
46 | irc.umich.edu: YES
47 | irc.isdnet.fr: YES
48 | irc.lightning.net: YES
49 | efnet.vuurwerk.nl: YES
50 | irc.plur.net: YES
51 | 
52 | 
53 | 54 |

55 | 56 | Click Here to go back.
57 | 58 | 59 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0003.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Voting admins with multiple servers
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: ahnberg (irc.du.se)
6 | Called on: 01/30/01
7 | Ended on: 02/13/01
8 | Status: PASSED (yes: 16, no: 1, abstain: 0, elig: ~25)

9 | 10 | Description:

11 | 12 |
13 | 
14 | Each organization that runs an EFNet server is given 1 vote, provided that the
15 | person voting does not already vote for another server.
16 | 
17 | Specific cases, including but not limited to admins appointing "voting admins" to
18 | vote on their behalf for multiple servers will be dealt with on a case by case
19 | basis as detailed in the previous vote:
20 | 
21 | 4) In case one admin represents multiple servers that can be
22 | seen as one, we (the admins) should discuss the number of
23 | votes that server gets. If there is failure to agree, it will be decided by vote.
24 | 
25 | 
26 | Details:
27 | 
28 | irc.du.se: YES
29 | irc.lightning.net: YES
30 | irc.total.net: YES
31 | irc.emory.edu: YES
32 | irc.colorado.edu: YES
33 | irc.isdnet.fr: YES
34 | irc.umn.edu: YES
35 | efnet.vuurwerk.nl: YES
36 | irc.core.com: YES
37 | irc.stanford.edu: YES
38 | irc.ins.net.uk: YES
39 | irc.hemmet.chalmers.se: YES
40 | irc.light.se: YES
41 | irc.prison.net: YES
42 | irc2.magic.ca: YES
43 | irc.rt.ru: YES
44 | irc.plur.net: NO
45 | 
46 | 
47 | 48 |

49 | 50 | Click Here to go back.
51 | 52 | 53 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0004.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Hostname Spoofing
4 | Called by: MrPerfect (irc.core.com)
5 | Seconded by: Xref (irc.umich.edu)
6 | Called on: 02/22/01
7 | Ended on: 03/08/01
8 | Status: PASSED (yes: 16, no: 4, abstain: 0, elig: ~25)

9 | 10 | Description:

11 | 12 |
13 | 
14 | I'm using the default end date. I hope thats ok.
15 | 
16 | Purpose: To set guidelines for hostname spoofing.
17 | 
18 | Content: A server admin may only spoof domains for which they or the end-user 
19 | has ownership (i.e. billing contact for) of said domain. Spoofing non-existant 
20 | domains shall be allowed. However, if it becomes known to the admin or user 
21 | that the domain has been taken or under ownership of a person other than 
22 | end-user or admin and niether party has obtained permission from the domain 
23 | owner, said spoof shall be revoked.
24 | 
25 | Additionally, spoofing non-existant tld's shall be allowed provided fake tld 
26 | does not exceed 4 characters. (i.e. 5 chars or more is deemed illegal).
27 | 
28 | The admin takes responsibility for any spoofs on their server and should 
29 | revoke immediately upon notification of abuse from a "trusted" party. (i.e. 
30 | an oper)
31 | 
32 | Reasoning: The top portion is self-explanitory. The TLD portion comes from 
33 | a concern that I have seen long faked tld's mess with monitor bots and 
34 | scripts/clients in unpredictable ways. The final part, again should be 
35 | common sense.
36 | 
37 | That should do it unless I forgot something or went too far over the edge.
38 | 
39 | 
40 | Details:
41 | 
42 | irc.core.com: YES
43 | irc.emory.edu: NO
44 | irc.plur.net: YES
45 | irc.lightning.net: YES
46 | irc.inter.net.il: YES
47 | irc.rt.ru: NO
48 | irc.umn.edu: YES
49 | irc.light.se: YES
50 | irc.colorado.edu: YES
51 | irc.du.se: YES
52 | irc.umich.edu: YES
53 | irc.hemmet.chalmers.se: YES
54 | irc2.magic.ca: YES
55 | efnet.vuurwerk.nl: YES
56 | irc.isdnet.fr: YES
57 | irc.ins.net.uk: YES
58 | irc.exodus.net: NO
59 | irc.gigabell.de: NO
60 | *.gblx.net: YES
61 | irc.prison.net: YES
62 | 
63 | 
64 | 65 |

66 | 67 | Click Here to go back.
68 | 69 | 70 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0005.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Relinquishing right to vote
4 | Called by: squrl (irc.exodus.net)
5 | Seconded by: Tsk (irc.lightning.net)
6 | Called on: 02/28/01
7 | Ended on: 03/14/01
8 | Status: PASSED (yes: 18, no: 0, abstain: 0, elig: ~25)

9 | 10 | Description:

11 | 12 |
13 | 
14 | If any server has not signed up, having been duly notified, by a reasonable date,
15 | 3/14/01, the end of this vote, this list having been existant for some time now
16 | and everyone contacted, their server forfeits the right to be counted in the total
17 | votes required, rather than counting as an abstention.
18 | 
19 | If they later choose to be represented, they may sign up, and from that time
20 | forward, be counted.
21 | 
22 | On linking of a new server, they should be notified of this system, and given two
23 | weeks to join, or else forfeit their right to be counted until such time as they
24 | choose to sign up for representation.
25 | 
26 | Purpose: to limit "useless" numbers in the system, making it more readily possible
27 | to achieve a majority.
28 | 
29 | 
30 | Details:
31 | 
32 | irc.core.com: YES
33 | irc.emory.edu: YES
34 | irc.plur.net: YES
35 | irc.lightning.net: YES
36 | irc.inter.net.il: YES
37 | irc.rt.ru: YES
38 | irc.umn.edu: YES
39 | irc.concentric.net: YES
40 | irc.light.se: YES
41 | irc.du.se: YES
42 | irc.colorado.edu: YES
43 | irc.umich.edu: YES
44 | efnet.vuurwerk.nl: YES
45 | irc.isdnet.fr: YES
46 | irc.exodus.net: YES
47 | irc.ins.net.uk: YES
48 | irc.gigabell.de: YES
49 | irc.prison.net: YES
50 | 
51 | 
52 | 53 |

54 | 55 | Click Here to go back.
56 | 57 | 58 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0006.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Hostname spoofing 2
4 | Called by: squrl (irc.exodus.net)
5 | Seconded by: Tsk (irc.lightning.net)
6 | Called on: 02/28/01
7 | Ended on: 03/14/01
8 | Status: PASSED (yes: 14, no: 4, abstain: 1, elig: ~25)

9 | 10 | Description:

11 | 12 |
13 | 
14 | Purpose: To set guidelines for hostname spoofing.
15 | 
16 | Content: A server admin may only spoof domains for which they or the end-user has
17 | ownership (i.e. billing contact for) of said domain. Spoofing non-existant domains
18 | shall be not allowed. However, if it becomes known to the admin or user that the
19 | domain has been taken or under ownership of a person other than end-user or admin
20 | and niether party has obtained permission from the domain owner, said spoof shall
21 | be revoked.
22 | 
23 | Also, if an admin on a server refuses to remove a spoof, having been shown
24 | evidence of abuse by the user using a spoof, the admin may be called responsible
25 | for allowing abuse to continue on their server.
26 | 
27 | Spoofing is a protection for users on the network, one some say should only be
28 | limited to opers. That, perhaps, is a bit harsh, although I do agree to some
29 | extent. However, allowing spoofing to non-registered/non-existant domains because
30 | someone thinks its cool, but doesn't want to pay for the domain, or have it appear
31 | as a real address is both childish, and confuses the issue much more than is
32 | necessary.
33 | 
34 | 
35 | Details:
36 | 
37 | irc.core.com: YES
38 | irc.emory.edu: YES
39 | irc.plur.net: YES
40 | irc.lightning.net: YES
41 | irc.inter.net.il: ABSTAIN
42 | irc.rt.ru: NO
43 | irc.umn.edu: YES
44 | irc.concentric.net: YES
45 | irc.light.se: YES
46 | irc.du.se: YES
47 | irc.colorado.edu: NO
48 | irc.umich.edu: NO
49 | irc2.magic.ca: YES
50 | efnet.vuurwerk.nl: YES
51 | irc.isdnet.fr: YES
52 | irc.exodus.net: YES
53 | irc.ins.net.uk: YES
54 | irc.gigabell.de: NO
55 | irc.prison.net: YES
56 | 
57 | 
58 | 59 |

60 | 61 | Click Here to go back.
62 | 63 | 64 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0007.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Relinquish right to vote 2
4 | Called by: grievah (irc.isdnet.fr)
5 | Seconded by: ariel (irc.inter.net.il)
6 | Called on: 02/28/01
7 | Ended on: 03/14/01
8 | Status: PASSED (yes: 14, no: 2, abstain: 0, elig: ~25)

9 | 10 | Description:

11 | 12 |
13 | 
14 | At any given point in time, voting right may be removed from servers that match
15 | BOTH following criterias:
16 | 
17 | a. have not voted for (at least) a month
18 | b. have not voted for the last 4 votes
19 | 
20 | These servers would then have to re-apply, as specified in the other vote
21 | "Relinquish right to vote".
22 | 
23 | Purpose: also limit "useless" numbers in the system, making it more readily
24 | possible to achieve a majority.
25 | 
26 | 
27 | Details:
28 | 
29 | irc.core.com: YES
30 | irc.emory.edu: NO
31 | irc.plur.net: YES
32 | irc.inter.net.il: YES
33 | irc.rt.ru: YES
34 | irc.umn.edu: YES
35 | irc.concentric.net: YES
36 | irc.light.se: YES
37 | irc.colorado.edu: NO
38 | irc.du.se: YES
39 | irc.umich.edu: YES
40 | efnet.vuurwerk.nl: YES
41 | irc.isdnet.fr: YES
42 | irc.exodus.net: YES
43 | irc.gigabell.de: YES
44 | irc.prison.net: YES
45 | 
46 | 
47 | 48 |

49 | 50 | Click Here to go back.
51 | 52 | 53 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0008.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Advance notification of Oper Additions
4 | Called by: riedel (efnet.vuurwerk.nl)
5 | Seconded by: madmax (irc.ins.net.uk)
6 | Called on: 03/10/01
7 | Ended on: 03/24/01
8 | Status: NOT PASSED (yes: 12, no: 10, abstain: 2, elig: ~30)

9 | 10 | Description:

11 | 12 |
13 | 
14 | Hi Folks,
15 | 
16 | EU-EFNet already has a simular policy, but i think it would be a good to have network wide.
17 | 
18 | The Proposed :
19 | 
20 | 1. When an administrator of a server wants to add a new (local or global) oper, a notification
21 | of that intent shall be sent approximately 1 week in advance to a designated e-mail address
22 | which will go to all subscribed EFNet administrators.
23 | 
24 | The thought behind this is that the administrator has the chance to find out things that were
25 | unknown to him/her at that time (ie : proposed oper X has a severe record of abuse) and it
26 | would inform the other administrators about new oper addition & to make comments/remarks/etc.
27 | 
28 | 2. The administrators do _not_ have a formal vote about the addition of the new oper, but
29 | merely a suggesting function.
30 | 
31 | 3. At no time there are penalties for not following up on the advice of (the majority of) the
32 | EFNet admin community. New Oper Additions will remain the sole responsibility of the server
33 | administrator. It's just that an Advance notification of 1 week would be in order.
34 | 
35 | If this policy contradicts with already in-place regional policies, the existing regional
36 | policies will take precedence above this one, with exception of what's described under 1,
37 | advance notification.
38 | 
39 | Details:
40 | 
41 | irc.core.com: YES
42 | irc.plur.net: NO
43 | irc.emory.edu: NO
44 | irc.total.net: NO
45 | irc.lightning.net: NO
46 | irc.inter.net.il: YES
47 | irc.lagged.org: NO
48 | irc.rt.ru: NO
49 | irc.umn.edu: NO
50 | irc.concentric.net: YES
51 | irc.light.se: YES
52 | irc.du.se: YES
53 | irc.umich.edu: NO
54 | irc.hemmet.chalmers.se: YES
55 | irc2.magic.ca: YES
56 | efnet.vuurwerk.nl: YES
57 | irc.stanford.edu: YES
58 | irc.ins.net.uk: YES
59 | irc.isdnet.fr: ABSTAIN
60 | irc.exodus.net: YES
61 | *.gblx.net: NO
62 | irc.gigabell.de: YES
63 | irc.prison.net: ABSTAIN
64 | irc.magic.ca: NO
65 | 
66 | 
67 | 68 |

69 | 70 | Click Here to go back.
71 | 72 | 73 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0009.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Definition of majority and what is required for a vote to pass
4 | Called by: madmax (irc.ins.net.uk)
5 | Seconded by: grievah (irc.isdnet.fr)
6 | Called on: 03/13/01
7 | Ended on: 03/27/01
8 | Status: PASSED (yes: 19, no: 0, abstain: 3, elig: ~30)

9 | 10 | Description:

11 | 12 |
13 | 
14 | We originally voted on:
15 | "1) Definition of a majority vote
16 | A vote will be considered "passed" if: 
17 | (number of yes votes) / (number of cast votes) >= 51%
18 | provided that at least 51% of eligible servers cast a vote."
19 | 
20 | However this would make a No vote equal to an Abstaination from voting.
21 | 
22 | The proposal is to superceed the previous agreement with this:
23 | 
24 | Definition of a (simple) Majority vote:
25 | A vote will be considered "passed" by majority vote if:
26 | (number of YES votes) / (number of YES and NO votes) >= 51%
27 | provided that at least 51% of eligible servers cast a YES or NO vote)
28 | 
29 | Therefore abstaining is (as far as a count is concerned) the same as not turning up, but
30 | without the blackmark against the admin for the lack of vote.
31 | 
32 | This is a vote purely for the definition of a simple majority (as in the default voting result
33 | requirements).  We may decide at a later date that some decisions require their own system, for
34 | example a 2/3rd majority or quorum.
35 | 
36 | Details:
37 | 
38 | irc.core.com: YES
39 | irc.lightning.net: ABSTAIN
40 | irc.total.net: YES
41 | irc.inter.net.il: YES
42 | irc.lagged.org: YES
43 | irc.rt.ru: YES
44 | irc.umn.edu: YES
45 | irc.concentric.net: ABSTAIN
46 | irc.light.se: YES
47 | irc.colorado.edu: YES
48 | irc.du.se: YES
49 | irc.umich.edu: YES
50 | irc.hemmet.chalmers.se: YES
51 | irc2.magic.ca: YES
52 | efnet.vuurwerk.nl: YES
53 | irc.stanford.edu: YES
54 | irc.isdnet.fr: YES
55 | irc.ins.net.uk: YES
56 | irc.gigabell.de: YES
57 | *.gblx.net: YES
58 | irc.prison.net: ABSTAIN
59 | irc.magic.ca: YES
60 | 
61 | 
62 | 63 |

64 | 65 | Click Here to go back.
66 | 67 | 68 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0010.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: US routing reorganization (US admins only please)
4 | Called by: squrl (irc.exodus.net)
5 | Seconded by: Tsk (irc.lightning.net)
6 | Called on: 03/15/01
7 | Ended on: 03/29/01
8 | Status: PASSED (yes: 8, no: 0, abstain: 1, elig: 12)

9 | 10 | Description:

11 | 12 |
13 | 
14 | As some of you may have seen on routing, I would like to call a vote for the restructuring of
15 | the US routing commitee. As the admins are present here, it seems the best forum, and would be
16 | appreciated if admins from outside the US would abstain/ignore this issue.
17 | 
18 | 
19 | For under 10 members of the routing comittee, there be one US representative named for each
20 | routing server on the comittee. This person need not be associated with a routing server, as
21 | the admins for the routing server will be on the committe, but must be chosen from the US. The
22 | representatives must show an understanding of routing, both on irc and in general. It need not
23 | be a current oper, although that would be preferable, as they can not actually "route" unless
24 | they are a global oper.
25 | The representatives would be chosen by a vote of US admins.                     
26 | The reason for the restriction to the US: 
27 | Up until this time, it has been agreed that each region maintains responsibility for linking
28 | and delinking of servers within their region.        
29 | The global admin list has been doing quite well at policy changes, but it is my feeling we
30 | should continue to maintain our autonomy with regards to links/delinks in our region.
31 | As such, I would like to limit the vote, and candidates, should this be accepted to US admins
32 | only.
33 | At this time, we would be electing 4 additional members to the routing committee, for the 4
34 | operational hubs. Once the status of best is determined, a fifth could be elected. In the event
35 | that the number of routing hubs exceeds 5, the number of elected representatives will either
36 | remain at 5, or be reduced, based on the current feeling of the committee towards whether or
37 | not there are too many people involved to be of use. 
38 | I would recommend a 6 month period for the representatives, to avoid anyone being burnt-out, or
39 | losing enthusiasm about the job.                    
40 | Routing will also maintain responsibility for selecting new hubs based on their benefit to the
41 | network and necessity.
42 | I would also like to specify that a non-routing admin member of routing may be removed from the
43 | committee at a majority vote of either US routing or US admins, if his behavior is questionable
44 | in the eyes of the other members.
45 | I would also like to stipulate that the elected be of a well demonstrated trust-worthy nature
46 | and acceptible to their peers on the committe.
47 | This is not to imply that we are looking for a lack of disagreement, or more of the same voice
48 | to pass issues with out question. The point of this vote is an attempt to revitalize the US
49 | portion of efnet and bring in fresh blood and new perspectives. However, someone both competent
50 | and trustworthy by all would be preferable to someone who is merely "well-liked".
51 | If this vote is passed, it will then be up to the US admins to select and vote in their
52 | representatives.
53 | 
54 | Details:
55 | 
56 | irc.emory.edu: YES
57 | irc.lightning.net: YES
58 | irc.lagged.org: YES
59 | irc.umn.edu: YES
60 | irc.stanford.edu: YES
61 | irc.concentric.net: ABSTAIN
62 | irc.exodus.net: YES
63 | *.gblx.net: YES
64 | irc.umich.edu: YES
65 | 
66 | 
67 | 68 |

69 | 70 | Click Here to go back.
71 | 72 | 73 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0011.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: violation of list privacy
4 | Called by: squrl (irc.exodus.net)
5 | Seconded by: Tsk (irc.lightning.net)
6 | Called on: 03/15/01
7 | Ended on: 03/29/01
8 | Status: PASSED (yes: 18, no: 0, abstain: 1, elig: ~30)

9 | 10 | Description:

11 | 12 |
13 | 
14 | It was my understanding in the outset, this list was to be a closed forum for discussion free
15 | from threat of harrassment.
16 | While I hate to do so, since it has recently come to light that the contents of this list are
17 | being passed beyond the agreed upon scope, that being the subscribers to this list, and feeling
18 | badly about an obvious violation of trust so new into this endeavour, I would like to propose
19 | something setting an official policy concerning list privacy. Being as some people have posted
20 | phone numbers and controversial opinions, I feel certain that knowing the audience to which it
21 | is addressed would be a comfort to all involved.
22 | 
23 | In order to provide a safe environment for discussion, without threat of retribution from any
24 | party who may feel harmed by decisions from this list, I would like to make it a violation to
25 | make public to anyone besides the known audience, the subscribers, discussions on this list. 
26 | While topics and outcomes are a matter of public concern, I don't think someone has the right
27 | to make another person's opinion public without the permission of the person stating that
28 | opinion.
29 | 
30 | This vote is to set the policy as to whether or not this list is indeed private, and forwarding
31 | of emails and explicit information is considered a violation of the trust we should as admins
32 | place in each other.
33 | I would like to recommend a one month suspension of list priveledges for anyone in violation of
34 | this should it exist, however, as we have had so many amendments lately, I would like to leave
35 | enforcement of the policy to a later vote, following discussion, and simply make this a policy
36 | vote.
37 | 
38 | 
39 | Details:
40 | 
41 | irc.emory.edu: YES
42 | irc.lightning.net: YES
43 | irc.total.net: YES
44 | irc.inter.net.il: YES
45 | irc.lagged.org: YES
46 | irc.rt.ru: YES
47 | irc.concentric.net: ABSTAIN
48 | irc.light.se: YES
49 | irc.du.se: YES
50 | irc.umich.edu: YES
51 | irc.hemmet.chalmers.se: YES
52 | irc2.magic.ca: YES
53 | efnet.vuurwerk.nl: YES
54 | irc.stanford.edu: YES
55 | irc.isdnet.fr: YES
56 | irc.exodus.net: YES
57 | irc.gigabell.de: YES
58 | *.gblx.net: YES
59 | irc.magic.ca: YES
60 | 
61 | 
62 | 
63 | 64 |

65 | 66 | Click Here to go back.
67 | 68 | 69 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0012.shtml: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/grawity/irc-docs/d6941670a9013cfe81f0493ef1ddf28cfe6585b9/misc/voting.efnet.org/archives/0012.shtml -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0013.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Mininum requirement for irc admins
4 | Called by: ariel (irc.inter.net.il)
5 | Seconded by: madmax (irc.ins.net.uk)
6 | Called on: 03/25/01
7 | Ended on: 04/08/01
8 | Status: NOT PASSED (yes: 4, no: 6, abstain: 2 elig: ~30)

9 | 10 | Description:

11 | 12 |
13 | 
14 | A set of minimum requirements for the professional level
15 | of irc-admins must be added as a part of the server linking
16 | guidelines. The fact that new admins are kind of clueless
17 | adversly affects this network, and lowers the overall
18 | professional quality of EFNet admins, which was/is still
19 | a thing we take pride in.
20 | I claim that admins should pass a set of requirements as
21 | well as the servers they propose. After all, a good server
22 | is a balance between quality networking/hardware, and it's
23 | staff. The server admin is the leader of his/her server,
24 | and the staff will look and act like him/her.
25 | 
26 | --Ariel
27 | 
28 | 
29 | Details:
30 | 
31 | efnet.cs.hut.fi: YES
32 | efnet.vuurwerk.nl: NO
33 | irc.plur.net: NO
34 | irc.lightning.net: ABSTAIN
35 | irc.total.net: NO
36 | irc.lagged.org: NO
37 | irc.stanford.edu: YES
38 | irc.ins.net.uk: NO
39 | irc.concentric.net: NO
40 | irc.light.se: YES
41 | irc.colorado.edu: YES
42 | irc.du.se: YES
43 | irc.umich.edu: ABSTAIN
44 | 
45 | 
46 | 47 |

48 | 49 | Click Here to go back.
50 | 51 | 52 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0015.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Notification of oper additions
4 | Called by: riedel (efnet.vuurwerk.nl)
5 | Seconded by: ahnberg (irc.du.se)
6 | Called on: 04/13/01
7 | Ended on: 04/27/01
8 | Status: NOT PASSED (yes: 12, no: 14, abstain: 0, elig: 29)

9 | 10 | Description:

11 | 12 |
13 | 
14 | Hi again,
15 | 
16 | As per Tsk's suggestion i'm now calling a vote on notification of oper additions,
17 | instead of advance notification of oper additions.
18 | 
19 | Proposal :
20 | 
21 | Every new oper addition must be sent to a designated e-mail address, which will send
22 | the mail to all subscribed EFNet opers/admins. (Obviously this list has to be set up if
23 | this vote is passed, and someone needs to 'admin' it... but that's beyond the scope of
24 | this CFV)
25 | 
26 | This policy will not affect in-place regional policies regarding notification of oper
27 | additions, nor will in-place regional policies affect the global policy about said
28 | notification.
29 | 
30 | 
31 | Details:
32 | 
33 | efnet.demon.co.uk: YES
34 | irc.emory.edu: NO
35 | irc.mcs.net: NO
36 | irc.plur.net: NO
37 | irc.total.net: NO
38 | irc.lightning.net: NO
39 | irc.inter.net.il: YES
40 | irc.solidstreaming.net: NO
41 | irc.lagged.org: NO
42 | irc.rt.ru: NO
43 | irc.concentric.net: YES
44 | irc.light.se: YES
45 | irc.colorado.edu: NO
46 | irc.du.se: YES
47 | irc.umich.edu: NO
48 | irc.hemmet.chalmers.se: YES
49 | irc2.magic.ca: NO
50 | efnet.cs.hut.fi: YES
51 | efnet.vuurwerk.nl: YES
52 | irc.stanford.edu: YES
53 | irc.ins.net.uk: NO
54 | irc.isdnet.fr: YES
55 | *.gblx.net: NO
56 | irc.gigabell.de: YES
57 | irc.prison.net: YES
58 | irc.magic.ca: NO
59 | 
60 | 
61 | 62 |

63 | 64 | Click Here to go back.
65 | 66 | 67 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0016.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: jupes.int (FINAL)
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: madmax (irc.ins.net.uk)
6 | Called on: 04/19/01
7 | Ended on: 04/26/01
8 | Status: PASSED (yes: 25, no: 0, abstain: 3, elig: 29)

9 | 10 | Description:

11 | 12 |
13 | 
14 | Jupes tool proposed (and created) by tay and comstud as described at:
15 | 
16 | http://voting.efnet.org/proposals/jupes.int.txt
17 | 
18 | 
19 | Details:
20 | 
21 | efnet.demon.co.uk: YES
22 | irc.emory.edu: YES
23 | irc.mcs.net: YES
24 | irc.plur.net: YES
25 | irc.lightning.net: YES
26 | irc.total.net: YES
27 | irc.inter.net.il: YES
28 | irc.lagged.org: YES
29 | irc.solidstreaming.net: YES
30 | irc.rt.ru: YES
31 | irc.umn.edu: YES
32 | irc.concentric.net: YES
33 | irc.light.se: YES
34 | irc.colorado.edu: ABSTAIN
35 | irc.du.se: YES
36 | irc.umich.edu: YES
37 | irc.hemmet.chalmers.se: YES
38 | irc2.magic.ca: YES
39 | efnet.cs.hut.fi: YES
40 | efnet.vuurwerk.nl: YES
41 | irc.isdnet.fr: ABSTAIN
42 | irc.exodus.net: YES
43 | irc.stanford.edu: YES
44 | irc.ins.net.uk: ABSTAIN
45 | *.gblx.net: YES
46 | irc.gigabell.de: YES
47 | irc.prison.net: YES
48 | irc.magic.ca: YES
49 | 
50 | 
51 | 52 |

53 | 54 | Click Here to go back.
55 | 56 | 57 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0017.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: client hostname spoofing policy (FINAL)
4 | Called by: wjr (irc.concentric.net)
5 | Seconded by: Xref (irc.umich.edu)
6 | Called on: 05/17/01
7 | Ended on: 05/31/01
8 | Status: PASSED (yes: 22, no: 3, abstain: 0, elig: 29)

9 | 10 | Description:

11 | 12 |
13 | 
14 | This vote supercedes (and obsoletes) all previous votes on this topic and will
15 | hopefully be the last one we ever have to call on this issue. Let this stumbling be the
16 | lesson we were destined to learn as we grow as a governing body and realize we are all
17 | human and make mistakes. I hope this proposal is met with the same approval in
18 | votingland as it was while we were discussing it.
19 | 
20 | For the text of the proposal, please view it at:
21 | https://voting.efnet.org/proposals/spoof-proposal.txt
22 | 
23 | For the record, a vote of "YES" to the above-referenced proposal will result in all
24 | previous "policies" or "rules" about hostname spoofing on efnet being removed from the
25 | official record (except for historical reference) and this policy will be instated in
26 | its place. A vote of "NO" will result in chaos and mass-hysteria -- just kidding,
27 | actually, a vote of "NO" will effect no change whatsoever to the current policies on
28 | hostname spoofing on the efnet irc network. An "ABSTAIN" vote will of course merely
29 | contribute to quorum. Thank you for your time.
30 | 
31 | Details:
32 | 
33 | irc.plur.net: YES
34 | irc.emory.edu: YES
35 | irc.lightning.net: YES
36 | irc.lagged.org: YES
37 | irc.solidstreaming.net: YES
38 | irc.rt.ru: YES
39 | irc.homelien.no: YES
40 | irc.umn.edu: YES
41 | irc.concentric.net: YES
42 | irc.light.se: YES
43 | irc.colorado.edu: YES
44 | irc.du.se: YES
45 | irc.umich.edu: YES
46 | irc.hemmet.chalmers.se: YES
47 | irc2.magic.ca: NO
48 | efnet.cs.hut.fi: YES
49 | efnet.vuurwerk.nl: YES
50 | irc.etsmtl.ca: NO
51 | irc.isdnet.fr: YES
52 | irc.ins.net.uk: YES
53 | irc.gigabell.de: YES
54 | *.gblx.net: YES
55 | irc.does-not-exist.com: YES
56 | irc.prison.net: YES
57 | irc.magic.ca: NO
58 | 
59 | 
60 | 61 |

62 | 63 | Click Here to go back.
64 | 65 | 66 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0018.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Moving clones/drones/stats from services.us into services.int
4 | Called by: comstud (irc.concentric.net)
5 | Seconded by: Disciple (irc.solidstreaming.net)
6 | Called on: 07/06/01
7 | Ended on: 07/13/01
8 | Status: PASSED (yes: 19, no: 0, abstain: 1, elig: 32)

9 | 10 | Description:

11 | 12 |
13 | 
14 | Tcms rely on /msging SERVICES for some of their clones and drones checking, and I would
15 | like to move that nickname over to services.int to use there for the jupes related
16 | commands and so forth.  However, before I can use it there, it needs to support
17 | services.us's clones and drones commands in order to not break tcms.  Therefore, I'd
18 | like to move those commands as well as the stats information into services.int from
19 | services.us.  The format of the clones and drones commands should remain the same, as
20 | well as the format of the output.  The stats output may change, but nothing relies
21 | on that, at least for anything important.
22 | 
23 | Since this is pretty simple, I've proposed the vote end in a week.
24 | 
25 | Details:
26 | 
27 | irc.lightning.net: YES
28 | irc.solidstreaming.net: YES
29 | irc.inter.net.il: YES
30 | irc.carrier1.net.uk: YES
31 | irc.concentric.net: YES
32 | irc.light.se: YES
33 | irc.du.se: YES
34 | irc.umich.edu: YES
35 | irc2.magic.ca: YES
36 | efnet.cs.hut.fi: YES
37 | efnet.vuurwerk.nl: YES
38 | irc.mindspring.com: YES
39 | irc.etsmtl.ca: YES
40 | irc.powersurfr.com: YES
41 | irc.ins.net.uk: YES
42 | irc.isdnet.fr: YES
43 | irc.gigabell.de: YES
44 | *.gblx.net: ABSTAIN
45 | irc.prison.net: YES
46 | irc.magic.ca: YES
47 | 
48 | 
49 | 50 |

51 | 52 | Click Here to go back.
53 | 54 | 55 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0019.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: prysm/therose to run operlist
4 | Called by: riedel (efnet.vuurwerk.nl)
5 | Seconded by: thomas (irc.magic.ca)
6 | Called on: 07/11/01
7 | Ended on: 07/25/01
8 | Status: PASSED (yes: 26, no: 0, abstain: 3, elig: 32)

9 | 10 | Description:

11 | 12 |
13 | 
14 | TheRose and Prysm are both on board as a team to run Operlist
15 | and be our go-betweens from voting@ to the Operlist.
16 | Operlist will be a closed forum, only for opers.
17 | No /lusers allowed ;)
18 | 
19 | They will be responsible for provding the Operlist with information we pass through on
20 | voting.
21 | 
22 | Details:
23 | 
24 | efnet.demon.co.uk: YES
25 | irc.mcs.net: YES
26 | irc.plur.net: ABSTAIN
27 | irc.lightning.net: YES
28 | irc.lagged.org: YES
29 | irc.solidstreaming.net: YES
30 | irc.inter.net.il: YES
31 | irc.rt.ru: YES
32 | irc.umn.edu: YES
33 | irc.homelien.no: YES
34 | irc.carrier1.net.uk: YES
35 | irc.concentric.net: YES
36 | irc.light.se: YES
37 | irc.du.se: YES
38 | irc.umich.edu: YES
39 | irc.hemmet.chalmers.se: YES
40 | irc2.magic.ca: YES
41 | efnet.cs.hut.fi: YES
42 | efnet.vuurwerk.nl: ABSTAIN
43 | irc-h.magic.ca: YES
44 | irc.mindspring.com: YES
45 | irc.powersurfr.com: ABSTAIN
46 | irc.exodus.net: YES
47 | irc.isdnet.fr: YES
48 | irc.ins.net.uk: YES
49 | irc.gigabell.de: YES
50 | *.gblx.net: YES
51 | irc.prison.net: YES
52 | irc.magic.ca: YES
53 | 
54 | 
55 | 
56 | 57 |

58 | 59 | Click Here to go back.
60 | 61 | 62 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0020.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: services.int reverse command
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: throwback (irc.powersurfr.com)
6 | Called on: 07/13/01
7 | Ended on: 07/20/01
8 | Status: PASSED (yes: 19, no: 4, abstain: 3, elig: 32)

9 | 10 | Description:

11 | 12 |
13 | 
14 | (another 1 week vote due to immediate relevence)
15 | 
16 | Chris (comstud) has coded a reverse command for the opless channel module of
17 | services.int, originally Tsk's idea.
18 | 
19 | In the event that a channel is taken over (via a compromised machine, hacked server,
20 | etc), any global oper can issue a "/msg services reverse #channel" command.  Services
21 | will join a client to the channel, lower ts by 1, and op the top-5-most-opped people
22 | according to its database.
23 | 
24 | I don't feel the need for more than 1 oper to concur on a reverse command, as more
25 | than one oper may not know the channel's story and requiring such would create a game
26 | of opers convincing each other to issue the command.
27 | 
28 | Details:
29 | 
30 | efnet.demon.co.uk: YES
31 | irc.plur.net: YES
32 | irc.mcs.net: NO
33 | irc.lightning.net: YES
34 | irc.solidstreaming.net: YES
35 | irc.lagged.org: YES
36 | irc.inter.net.il: YES
37 | irc.rt.ru: YES
38 | irc.carrier1.net.uk: YES
39 | irc.umn.edu: NO
40 | irc.concentric.net: YES
41 | irc.light.se: YES
42 | irc.du.se: YES
43 | irc.colorado.edu: ABSTAIN
44 | irc.umich.edu: YES
45 | irc.hemmet.chalmers.se: YES
46 | irc2.magic.ca: YES
47 | efnet.cs.hut.fi: ABSTAIN
48 | efnet.vuurwerk.nl: YES
49 | irc.mindspring.com: NO
50 | irc.powersurfr.com: YES
51 | irc.isdnet.fr: YES
52 | irc.ins.net.uk: YES
53 | *.gblx.net: ABSTAIN
54 | irc.prison.net: NO
55 | irc.magic.ca: YES
56 | 
57 | 
58 | 59 |

60 | 61 | Click Here to go back.
62 | 63 | 64 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0021.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: TS5
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: thomas (irc.magic.ca)
6 | Called on: 08/25/01
7 | Ended on: 09/08/01
8 | Status: PASSED (yes: 22, no: 0, abstain: 0, elig: 29)

9 | 10 | Description:

11 | 12 |
13 | 
14 | This vote is on the migration from TS3 to TS5 as 
15 | implemented in the technical document sent to the voting 
16 | list.  Specifically, this vote will remove the TS exeption 
17 | making it effectively impossible to hack ops on a split.
18 | 
19 | This vote should in no way "tie our hands", as we now have 
20 | services.int.  If realized in the future that we still 
21 | require an additional way to regain ops (to replace opers 
22 | being able to hack ops on splits), we can vote on a means 
23 | to do so in the future.  For now, we need to take this 
24 | preventative measure to reduce attacks on our servers.
25 | 
26 | Per this vote, all admins will be required to upgrade their 
27 | ircds to one that supports TS5 by the end of September.
28 | 
29 | TS5 should not be enabled on ANY server until Saturday 
30 | October 6th, at which time admins will have until the end 
31 | of Sunday October 7th to enable the feature in their ircds 
32 | (48 hrs).
33 | 
34 | The TS5 specification is at:
35 | 
36 | https://voting.efnet.org/docs/ts5.txt
37 | 
38 | The implementation may be slightly modified, but the 
39 | effects the same.
40 | 
41 | The results were as follows (summary at end):
42 | 
43 | efnet.demon.co.uk: YES
44 | irc.plur.net: YES
45 | irc.lightning.net: YES
46 | irc.solidstreaming.net: YES
47 | irc.lagged.org: YES
48 | irc.rt.ru: YES
49 | irc.carrier1.net.uk: YES
50 | irc.homelien.no: YES
51 | irc.umn.edu: YES
52 | irc.concentric.net: YES
53 | irc.light.se: YES
54 | irc.du.se: YES
55 | irc.colorado.edu: YES
56 | irc.umich.edu: YES
57 | irc.hemmet.chalmers.se: YES
58 | irc2.magic.ca: YES
59 | efnet.cs.hut.fi: YES
60 | efnet.vuurwerk.nl: YES
61 | irc.mindspring.com: YES
62 | irc.isdnet.fr: YES
63 | *.gblx.net: YES
64 | irc.magic.ca: YES
65 | 
66 | YES: 22
67 | NO: 0
68 | ABSTAIN: 0
69 | 
70 | The following servers did not vote:
71 | 
72 | irc.prison.net
73 | irc-h.magic.ca
74 | irc.inter.net.il
75 | irc.ins.net.uk
76 | irc.arcti.ca
77 | irc.qeast.net
78 | irc.efnet.pl
79 | 
80 | 
81 | 82 |

83 | 84 | Click Here to go back.
85 | 86 | 87 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0023.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Chanfix Notices
4 | Called by: comstud (irc-efnet.svc.us.xo.net)
5 | Seconded by: Salvation (irc.blessed.net)
6 | Called on: 05/14/03
7 | Ended on: 05/28/03
8 | Status: PASSED (yes: 28 , no: 5 , abstain: 2 , elig: 41)

9 | 10 | Description:

11 | 12 |
13 | Chanfix Notices
14 | 
15 | Notices will be sent to all users logged into Chanfix
16 | (OPERWALL is NOT to be used):
17 | 
18 | a) when an 'admin' sends a manual fix - obvious reasons
19 | b) when the oplist command is used.*
20 | 
21 | *Oplist is currently being abused by people that are just
22 | being nosey about the top 10 user@hosts in whatever channel
23 | they feel like being nosey about.  A notice sent to all
24 | logged in users will help deter this type of activity.
25 | :)  I hope.
26 | 
27 | (Chanfix Opers can sit in the official #chanfix channel if
28 | they don't want to stay logged in and still want to stay 'on
29 | top of things' chanfix related.)
30 | 
31 | 
32 | 
33 | Details:
34 | 
35 | efnet.xs4all.nl: ABSTAIN
36 | irc.servercentral.net: YES
37 | irc.limelight.us: YES
38 | efnet.demon.co.uk: YES
39 | irc.blessed.net: YES
40 | hub.se: YES
41 | irc.efnet.nl: YES
42 | irc.inter.net.il: YES
43 | irc.aloha.net: YES
44 | irc.easynews.com: YES
45 | irc.efnet.pl: YES
46 | irc.umn.edu: YES
47 | irc.weblook2k.com: YES
48 | ircd.lagged.org: YES
49 | irc.du.se: YES
50 | irc.umich.edu: YES
51 | irc.he.net: YES
52 | irc.inet.tele.dk: YES
53 | irc.arcti.ca: YES
54 | irc.isprime.com: NO
55 | irc.nac.net: YES
56 | irc.wh.verio.net: YES
57 | efnet.skynet.be: YES
58 | irc.mindspring.com: YES
59 | irc.aol.com: ABSTAIN
60 | irc.avalonworks.ca: NO
61 | irc.banetele.no: NO
62 | irc.isdnet.fr: YES
63 | irc.mpls.ca: YES
64 | irc.dkom.at: YES
65 | irc.daxnet.no: NO
66 | irc.choopa.net: YES
67 | irc.prison.net: YES
68 | irc.qeast.net: NO
69 | irc.vrfx.com: YES
70 | 
71 | YES: 28
72 | NO: 5
73 | ABSTAIN: 2
74 | 
75 | The following servers did not vote:
76 | 
77 | efnet.cs.hut.fi
78 | irc.homelien.no
79 | irc.hemmet.chalmers.se
80 | irc-efnet.svc.us.xo.net
81 | irc.secsup.org
82 | irc.desync.com
83 | 
84 | 
85 | 
86 | 87 |

88 | 89 | Click Here to go back.
90 | 91 | 92 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0024.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Maximum 3 Chanfix Opers per server entity.
4 | Called by: comstud (irc-efnet.svc.us.xo.net)
5 | Seconded by: lazymanic (efnet.demon.co.uk)
6 | Called on: 05/14/03
7 | Ended on: 05/29/03
8 | Status: PASSED (yes: 30, no: 4 , abstain: 1 , elig: 41)

9 | 10 | Description:

11 | 12 |
13 | Maximum 3 Chanfix Opers per server entity.
14 | 
15 | Allow 3 Chanfix Opers at maximum per server entity,
16 | including the admin or admins.  When an admin picks an Oper
17 | to be a Chanfix Oper (as opposed to picking him/herself), a
18 | notice must be sent 72 hours in advance to a global Admins
19 | list (voting?) to allow for objections.
20 | 
21 | This idea is based off the way EU allows for objections
22 | against any new global opers.  It won't be possible to end
23 | up with 5 ppl per server with access.  This should make
24 | it not necessary to make an oper a co-admin just for the
25 | sake of chanfix access, (or access to the mailing lists for
26 | that matter), etc.
27 |     As some would say 'If you don't have conf access, you're
28 | not an admin'...
29 | 
30 | 
31 | 
32 | Details:
33 | 
34 | efnet.xs4all.nl: YES
35 | irc.servercentral.net: YES
36 | irc.limelight.us: YES
37 | efnet.demon.co.uk: YES
38 | irc.blessed.net: YES
39 | hub.se: YES
40 | irc.efnet.nl: YES
41 | irc.inter.net.il: NO
42 | irc.aloha.net: YES
43 | irc.efnet.pl: YES
44 | irc.easynews.com: NO
45 | irc.umn.edu: YES
46 | irc.weblook2k.com: YES
47 | ircd.lagged.org: YES
48 | irc.du.se: YES
49 | irc.he.net: YES
50 | irc.umich.edu: YES
51 | irc.inet.tele.dk: YES
52 | irc.arcti.ca: ABSTAIN
53 | irc.isprime.com: YES
54 | irc.wh.verio.net: YES
55 | irc.nac.net: YES
56 | efnet.skynet.be: YES
57 | irc.mindspring.com: YES
58 | irc.aol.com: YES
59 | irc.avalonworks.ca: YES
60 | irc.banetele.no: YES
61 | irc.isdnet.fr: YES
62 | irc.mpls.ca: YES
63 | irc.dkom.at: YES
64 | irc.daxnet.no: NO
65 | irc.choopa.net: YES
66 | irc.prison.net: YES
67 | irc.qeast.net: NO
68 | irc.vrfx.com: YES
69 | 
70 | YES: 30
71 | NO: 4
72 | ABSTAIN: 1
73 | 
74 | The following servers did not vote:
75 | 
76 | efnet.cs.hut.fi
77 | irc.homelien.no
78 | irc.hemmet.chalmers.se
79 | irc-efnet.svc.us.xo.net
80 | irc.secsup.org
81 | irc.desync.com
82 | 
83 | 
84 | 85 |

86 | 87 | Click Here to go back.
88 | 89 | 90 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0026.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: US Voting System (US Regional)
4 | Called by: jafo (ircd.lagged.org)
5 | Seconded by: ik (irc.nac.net)
6 | Called on: 02/09/03
7 | Ended on: 02/20/03
8 | Status: PASSED (yes: 12, no: 2 , abstain: 1 , elig: ~19)

9 | 10 | Description:

11 | 12 |
13 | US Voting System
14 | 
15 | Open to US admins only, this vote is to determine the will
16 | of the US admin body as a whole so we can either move
17 | forward or put this issue to rest.
18 | 
19 | Do you think the US portion of EFnet should continue with a
20 | routing committee or do you prefer we form a US-wide voting
21 | system?
22 | 
23 | There has been some discussion and proposals put forth but
24 | participation from the admin body has been very limited
25 | which leads me to believe there isn't much interest in a US-
26 | wide voting system.
27 | 
28 | If we vote in favor of a US-wide system we should see ALL
29 | admins put forth some suggestions and participate in the
30 | discussions.
31 | 
32 | Voting YES indicates favor of a US-wide voting system.
33 | Voting NO indicates favor of the Routing Committee.
34 | 
35 | 
36 | 
37 | Details:
38 | 
39 | irc.servercentral.net: YES
40 | irc.limelight.us: YES
41 | irc.nac.net: YES
42 | irc.wh.verio.net: NO
43 | irc.mindspring.com: YES
44 | irc.aol.com: ABSTAIN
45 | irc.aloha.net: YES
46 | irc.umn.edu: YES
47 | irc.weblook2k.com: YES
48 | irc.concentric.net: YES
49 | ircd.lagged.org: YES
50 | irc.choopa.net: YES
51 | irc.secsup.uu.net: YES
52 | irc.umich.edu: YES
53 | irc.vrfx.com: NO
54 | 
55 | YES: 12
56 | NO: 2
57 | ABSTAIN: 1
58 | 
59 | The following servers did not vote:
60 | 
61 | irc.prison.net
62 | irc.easynews.com
63 | irc.lightning.net
64 | irc.blessed.net
65 | 
66 | 
67 | 68 |

69 | 70 | Click Here to go back.
71 | 72 | 73 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0028.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Rescind early vote conclusion entirely (US Regional)
4 | Called by: ik (irc.nac.net)
5 | Seconded by: Xref (irc.umich.edu)
6 | Called on: 04/22/03
7 | Ended on: 05/07/03
8 | Status: PASSED (yes: 11, no: 3 , abstain: 0 , elig: ~20)

9 | 10 | Description:

11 | 12 |
13 | Rescind early vote conclusion entirely
14 | 
15 | The current US Guidelines state:
16 | 
17 | - Votes may be closed early and the results posted to the
18 | admin community, once the required majority has been
19 | reached.
20 | 
21 | Vote YES will remove this paragraph from the guidelines
22 | entirely, meaning votes must last until the specified end
23 | date.
24 | 
25 | 
26 | Details:
27 | 
28 | irc.limelight.us: NO
29 | irc.servercentral.net: NO
30 | irc.blessed.net: YES
31 | irc.aloha.net: YES
32 | irc.umn.edu: YES
33 | irc.concentric.net: YES
34 | irc.weblook2k.com: YES
35 | ircd.lagged.org: YES
36 | irc.umich.edu: YES
37 | irc.isprime.com: NO
38 | irc.nac.net: YES
39 | irc.aol.com: YES
40 | irc.choopa.net: YES
41 | irc.vrfx.com: YES
42 | 
43 | YES: 11
44 | NO: 3
45 | ABSTAIN: 0
46 | 
47 | (- note : non-eligable server votes purged)
48 | 
49 | The following servers did not vote:
50 | 
51 | irc.prison.net
52 | irc.wh.verio.net
53 | irc.easynews.com
54 | irc.lightning.net
55 | irc.secsup.uu.net
56 | irc.mindspring.com
57 | 
58 | 
59 | 60 |

61 | 62 | Click Here to go back.
63 | 64 | 65 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0029.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Operspy (centralized with accountability)
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: Riedel (irc.efnet.nl)
6 | Called on: 05/20/03
7 | Ended on: 06/04/03
8 | Status: NOT PASSED (yes: 16, no: 17 , abstain: 1 , elig: 41)

9 | 10 | Description:

11 | 12 |
 13 | 
 14 | Operspy (centralized with accountability) [1/3]
 15 | 
 16 | This vote covers the following capabilities:
 17 | 
 18 | - See all +i clients in /who
 19 | - See all clients on +s/+p chans
 20 | - See +s/+p channels in /whois
 21 | - See channel keys/modes
 22 | 
 23 | This is one of three related votes.  Whichever one vote has
 24 | the largest number of YES responses, will be considered
 25 | passed.  The other two will be considered nullified.
 26 | 
 27 | If this vote passes, the above capabilities will be built
 28 | into services.  Policy dictating who will be given accounts
 29 | will mirror that of Chanfix accounts initially, and may be
 30 | changed at a later date.
 31 | 
 32 | Unless further policy is voted in at a later date, these
 33 | capabilities may only be used to combat drones.  Abuse of
 34 | these capabilities will be handled on a case-by-case basis
 35 | just as would abuse of /kill, /squit, sniffing, chanfix,
 36 | etc (again, until further policy is voted in at a later
 37 | date -- perhaps concurrently with these 3 votes!).
 38 | 
 39 | 
 40 | Details:
 41 | 
 42 | The results were as follows (summary at end):
 43 | 
 44 | efnet.xs4all.nl: NO
 45 | efnet.demon.co.uk: NO
 46 | irc.inter.net.il: YES
 47 | irc.aloha.net: NO
 48 | irc.easynews.com: YES
 49 | irc.umn.edu: NO
 50 | irc.weblook2k.com: NO
 51 | irc.du.se: YES
 52 | efnet.skynet.be: YES
 53 | irc.wh.verio.net: NO
 54 | irc.nac.net: YES
 55 | irc.avalonworks.ca: NO
 56 | irc.aol.com: NO
 57 | irc.isdnet.fr: NO
 58 | irc.mpls.ca: NO
 59 | irc.daxnet.no: NO
 60 | irc.prison.net: YES
 61 | irc.qeast.net: YES
 62 | irc.limelight.us: YES
 63 | irc.servercentral.net: NO
 64 | irc.blessed.net: NO
 65 | hub.se: YES
 66 | irc.efnet.nl: YES
 67 | irc.efnet.pl: YES
 68 | ircd.lagged.org: YES
 69 | irc.umich.edu: YES
 70 | irc.inet.tele.dk: NO
 71 | irc.arcti.ca: YES
 72 | irc.isprime.com: NO
 73 | irc.mindspring.com: YES
 74 | irc.banetele.no: NO
 75 | irc.dkom.at: ABSTAIN
 76 | irc.choopa.net: YES
 77 | irc.vrfx.com: NO
 78 | 
 79 | YES: 16
 80 | NO: 17
 81 | ABSTAIN: 1
 82 | 
 83 | The following servers did not vote:
 84 | 
 85 | efnet.cs.hut.fi
 86 | irc.homelien.no
 87 | irc.hemmet.chalmers.se
 88 | irc-efnet.svc.us.xo.net
 89 | irc.he.net
 90 | irc.secsup.org
 91 | irc.desync.com
 92 | 
 93 | 
94 | 95 |

96 | 97 | Click Here to go back.
98 | 99 | 100 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0030.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Operspy (local with accountability)
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: Riedel (irc.efnet.nl)
6 | Called on: 05/20/03
7 | Ended on: 06/04/03
8 | Status: PASSED (yes: 17, no: 16 , abstain: 1 , elig: 41)

9 | 10 | Description:

11 | 12 |
 13 | 
 14 | Operspy (local with accountability) [2/3]
 15 | 
 16 | This vote covers the following capabilities:
 17 | 
 18 | - See all +i clients in /who
 19 | - See all clients on +s/+p chans
 20 | - See +s/+p channels in /whois
 21 | - See channel keys/modes
 22 | 
 23 | This is one of three related votes.  Whichever one vote has
 24 | the largest number of YES responses, will be considered
 25 | passed.  The other two will be considered nullified.
 26 | 
 27 | If this vote passes, the above capabilities will be built
 28 | into each ircd.  The ircd will broadcast a notice as done
 29 | with /kill, bound to a usermode, for accountability.
 30 | Policy dictating who will be given accounts will be left to
 31 | the discression of each admin unless voted otherwise in the
 32 | future.
 33 | 
 34 | Unless further policy is voted in at a later date, these
 35 | capabilities may only be used to combat drones.  Abuse of
 36 | these capabilities will be handled on a case-by-case basis
 37 | just as would abuse of /kill, /squit, sniffing, chanfix,
 38 | etc (again, until further policy is voted in at a later
 39 | date -- perhaps concurrently with these 3 votes!).
 40 | 
 41 | 
 42 | Details:
 43 | 
 44 | The results were as follows (summary at end):
 45 | 
 46 | efnet.xs4all.nl: YES
 47 | efnet.demon.co.uk: NO
 48 | irc.inter.net.il: NO
 49 | irc.aloha.net: NO
 50 | irc.easynews.com: NO
 51 | irc.umn.edu: NO
 52 | irc.weblook2k.com: NO
 53 | irc.du.se: YES
 54 | efnet.skynet.be: YES
 55 | irc.nac.net: NO
 56 | irc.wh.verio.net: YES
 57 | irc.avalonworks.ca: YES
 58 | irc.aol.com: YES
 59 | irc.isdnet.fr: YES
 60 | irc.mpls.ca: ABSTAIN
 61 | irc.daxnet.no: NO
 62 | irc.prison.net: NO
 63 | irc.qeast.net: YES
 64 | irc.servercentral.net: NO
 65 | irc.limelight.us: YES
 66 | irc.blessed.net: YES
 67 | hub.se: NO
 68 | irc.efnet.nl: NO
 69 | irc.efnet.pl: YES
 70 | ircd.lagged.org: NO
 71 | irc.umich.edu: YES
 72 | irc.inet.tele.dk: NO
 73 | irc.arcti.ca: YES
 74 | irc.isprime.com: YES
 75 | irc.mindspring.com: YES
 76 | irc.banetele.no: YES
 77 | irc.dkom.at: YES
 78 | irc.choopa.net: NO
 79 | irc.vrfx.com: NO
 80 | 
 81 | YES: 17
 82 | NO: 16
 83 | ABSTAIN: 1
 84 | 
 85 | The following servers did not vote:
 86 | 
 87 | efnet.cs.hut.fi
 88 | irc.homelien.no
 89 | irc.hemmet.chalmers.se
 90 | irc-efnet.svc.us.xo.net
 91 | irc.he.net
 92 | irc.secsup.org
 93 | irc.desync.com
 94 | 
 95 | 
96 | 97 |

98 | 99 | Click Here to go back.
100 | 101 | 102 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0031.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Operspy (local with no accountability)
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: Riedel (irc.efnet.nl)
6 | Called on: 05/20/03
7 | Ended on: 06/04/03
8 | Status: NOT PASSED (yes: 15, no: 19 , abstain: 0 , elig: 41)

9 | 10 | Description:

11 | 12 |
 13 | 
 14 | Operspy (local with no accountability) [3/3]
 15 | 
 16 | This vote covers the following capabilities:
 17 | 
 18 | - See all +i clients in /who
 19 | - See all clients on +s/+p chans
 20 | - See +s/+p channels in /whois
 21 | - See channel keys/modes
 22 | 
 23 | This is one of three related votes.  Whichever one vote has
 24 | the largest number of YES responses, will be considered
 25 | passed.  The other two will be considered nullified.
 26 | 
 27 | If this vote passes, the above capabilities will be built
 28 | into each ircd.  The ircd will not broadcast a notice as
 29 | done with /kill, bound to a usermode, for accountability.
 30 | Policy dictating who will be given accounts will be left to
 31 | the discression of each admin unless voted otherwise in the
 32 | future.
 33 | 
 34 | Unless further policy is voted in at a later date, these
 35 | capabilities may only be used to combat drones.  Abuse of
 36 | these capabilities will be handled on a case-by-case basis
 37 | just as would abuse of /kill, /squit, sniffing, chanfix,
 38 | etc (again, until further policy is voted in at a later
 39 | date -- perhaps concurrently with these 3 votes!).
 40 | 
 41 | 
 42 | Details:
 43 | 
 44 | The results were as follows (summary at end):
 45 | 
 46 | efnet.xs4all.nl: NO
 47 | efnet.demon.co.uk: YES
 48 | irc.inter.net.il: NO
 49 | irc.aloha.net: NO
 50 | irc.easynews.com: NO
 51 | irc.umn.edu: NO
 52 | irc.weblook2k.com: YES
 53 | irc.du.se: YES
 54 | efnet.skynet.be: YES
 55 | irc.nac.net: NO
 56 | irc.wh.verio.net: YES
 57 | irc.avalonworks.ca: YES
 58 | irc.aol.com: NO
 59 | irc.isdnet.fr: NO
 60 | irc.mpls.ca: YES
 61 | irc.daxnet.no: NO
 62 | irc.prison.net: NO
 63 | irc.qeast.net: YES
 64 | irc.servercentral.net: YES
 65 | irc.limelight.us: YES
 66 | irc.blessed.net: YES
 67 | hub.se: NO
 68 | irc.efnet.nl: NO
 69 | irc.efnet.pl: NO
 70 | ircd.lagged.org: NO
 71 | irc.umich.edu: NO
 72 | irc.inet.tele.dk: YES
 73 | irc.arcti.ca: NO
 74 | irc.isprime.com: YES
 75 | irc.mindspring.com: NO
 76 | irc.banetele.no: YES
 77 | irc.dkom.at: NO
 78 | irc.choopa.net: NO
 79 | irc.vrfx.com: YES
 80 | 
 81 | YES: 15
 82 | NO: 19
 83 | ABSTAIN: 0
 84 | 
 85 | The following servers did not vote:
 86 | 
 87 | efnet.cs.hut.fi
 88 | irc.homelien.no
 89 | irc.hemmet.chalmers.se
 90 | irc-efnet.svc.us.xo.net
 91 | irc.he.net
 92 | irc.secsup.org
 93 | irc.desync.com
 94 | 
 95 | 
96 | 97 |

98 | 99 | Click Here to go back.
100 | 101 | 102 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0032.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: unapproved ircd hacks
4 | Called by: Xref (irc.umich.edu)
5 | Seconded by: ik (irc.nac.net)
6 | Called on: 06/08/03
7 | Ended on: 06/23/03
8 | Status: PASSED (yes: 20, no: 5 , abstain: 3 , elig: 41)

9 | 10 | Description:

11 | 12 |
 13 | 
 14 | unapproved ircd hacks
 15 | 
 16 | The purpose of this vote is to make running
 17 | unapproved "rogue" ircd modifications officially
 18 | unacceptable.  It is intended to allow room for admins to
 19 | modify their ircd, but also allow room for dealing with
 20 | modifications that others may consider unfair, abusive,
 21 | violations of privacy, etc.
 22 | 
 23 | Specifically, no server shall run any ircd modification
 24 | that violates user privacy including but not limited to
 25 | operspy capabilities without accountability, and/or
 26 | circumventing channel modes such as +i/+b.  Additionally,
 27 | no server shall sniff privmsg or other traffic at the ircd
 28 | or any other level for purposes other than troubleshooting
 29 | technical problems.
 30 | 
 31 | In the event that there is controversy over a particular
 32 | modification, the server(s) in question will remove the
 33 | modification immediately upon request from any admin until
 34 | a vote on the particular modification can be discussed,
 35 | called, and passed.
 36 | 
 37 | Violation of this policy is grounds for an immediate jupe
 38 | if deemed necessary by the number of admins required to
 39 | call a jupe, followed by a delink vote should at least 1
 40 | admin decide to call and second such a vote.
 41 | 
 42 | 
 43 | Details:
 44 | 
 45 | The results were as follows (summary at end):
 46 | 
 47 | efnet.xs4all.nl: YES
 48 | irc.servercentral.net: NO
 49 | irc.limelight.us: YES
 50 | irc.blessed.net: NO
 51 | irc.efnet.nl: YES
 52 | irc.aloha.net: YES
 53 | irc.umn.edu: YES
 54 | irc.efnet.pl: YES
 55 | irc.easynews.com: YES
 56 | irc.weblook2k.com: ABSTAIN
 57 | ircd.lagged.org: YES
 58 | irc.du.se: NO
 59 | irc.umich.edu: YES
 60 | irc.isprime.com: NO
 61 | irc.nac.net: YES
 62 | irc.wh.verio.net: NO
 63 | efnet.skynet.be: ABSTAIN
 64 | irc.mindspring.com: YES
 65 | irc.avalonworks.ca: YES
 66 | irc.secsup.org: ABSTAIN
 67 | irc.aol.com: YES
 68 | irc-efnet.svc.us.xo.net: YES
 69 | irc.isdnet.fr: YES
 70 | irc.dkom.at: YES
 71 | irc.choopa.net: YES
 72 | irc.prison.net: YES
 73 | irc.vrfx.com: YES
 74 | irc.qeast.net: YES
 75 | 
 76 | YES: 20
 77 | NO: 5
 78 | ABSTAIN: 3
 79 | 
 80 | The following servers did not vote:
 81 | 
 82 | efnet.cs.hut.fi
 83 | irc.banetele.no
 84 | irc.homelien.no
 85 | irc.hemmet.chalmers.se
 86 | efnet.demon.co.uk
 87 | irc.inter.net.il
 88 | irc.daxnet.no
 89 | irc.mpls.ca
 90 | irc.arcti.ca
 91 | irc.he.net
 92 | hub.se
 93 | irc.inet.tele.dk
 94 | irc.desync.com
 95 | 
96 | 97 |

98 | 99 | Click Here to go back.
100 | 101 | 102 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0033.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: OperSpy Accountability
5 | Date of conclusion : 30 Jun 2003 6 | Result: PASSED (yes: 16, no: 11, abstain: 4) 7 |
8 | Description:

9 | 10 |
11 | 
12 | The following vote has closed:
13 |                                                                                 
14 | Operspy accountability
15 |                                                                                 
16 | While clients on a local server should rightfully be
17 | policed by that server staff alone, Information obtained
18 | by use of operspy features is global. Channels being
19 | global in nature might reveal information sensitive to
20 | users on another server, outside jurisdiction of the
21 | initiating party. This vote calls for accountibility on
22 | both local and global uses of operspy features.
23 |                                                                                 
24 | Vote YES will require all uses of operspy, local and
25 | global, to be broadcast and logged globally.
26 |                                                                                 
27 | Vote NO will require only global uses of operspy to be
28 | broadcast and logged.
29 |                                                                                 
30 | The results were as follows (summary at end):
31 |                                                                                 
32 | efnet.xs4all.nl: YES
33 | irc.limelight.us: YES
34 | efnet.demon.co.uk: NO
35 | irc.servercentral.net: ABSTAIN
36 | irc.blessed.net: NO
37 | irc.inter.net.il: YES
38 | irc.efnet.nl: YES
39 | irc.aloha.net: YES
40 | irc.umn.edu: NO
41 | irc.efnet.pl: YES
42 | irc.easynews.com: NO
43 | irc.weblook2k.com: ABSTAIN
44 | ircd.lagged.org: YES
45 | irc.du.se: NO
46 | irc.umich.edu: YES
47 | irc.isprime.com: NO
48 | irc.wh.verio.net: NO
49 | irc.nac.net: YES
50 | efnet.skynet.be: YES
51 | irc.mindspring.com: YES
52 | irc.secsup.org: ABSTAIN
53 | irc.aol.com: YES
54 | irc.avalonworks.ca: NO
55 | irc.banetele.no: NO
56 | irc.isdnet.fr: YES
57 | irc.dkom.at: ABSTAIN
58 | irc.mpls.ca: NO
59 | irc.choopa.net: YES
60 | irc.prison.net: YES
61 | irc.vrfx.com: YES
62 | irc.qeast.net: NO
63 |                                                                                 
64 | YES: 16
65 | NO: 11
66 | ABSTAIN: 4
67 |                                                                                 
68 | The following servers did not vote:
69 |                                                                                 
70 | efnet.cs.hut.fi
71 | irc.homelien.no
72 | irc.hemmet.chalmers.se
73 | irc-efnet.svc.us.xo.net
74 | irc.daxnet.no
75 | irc.arcti.ca
76 | irc.he.net
77 | hub.se
78 | irc.inet.tele.dk
79 | irc.desync.com
80 | 
81 | 82 |

83 | 84 | Click Here to go back.
85 | 86 | 87 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0035.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: chan mode and conf changes
5 | Date of conclusion : 31 Jul 2003 6 | Result: PASSED (yes: 21, no: 1, abstain: 1) 7 |
8 | 9 | Description:

10 | 11 |
12 | The following vote has closed:
13 |                                                                                 
14 | chan mode and conf changes
15 |                                                                                 
16 | This vote calls for all servers to enable the channel modes
17 | +e (n!u@h mask exemption to +b) and +I (n!u@h mask exemption
18 | to +invite-only channels).  Permit all servers to configure
19 | their MAXBANS value to 100 as policy.
20 |                                                                                 
21 | Implementation of these changes shall take place within 2
22 | weeks after the close of vote.
23 |                                                                                 
24 | The results were as follows (summary at end):
25 |                                                                                 
26 | efnet.demon.co.uk: YES
27 | irc.servercentral.net: YES
28 | irc.blessed.net: YES
29 | irc.efnet.nl: YES
30 | irc.inter.net.il: YES
31 | irc.umn.edu: YES
32 | irc.efnet.pl: YES
33 | irc.easynews.com: YES
34 | ircd.lagged.org: ABSTAIN
35 | irc.du.se: YES
36 | irc.he.net: YES
37 | irc.umich.edu: YES
38 | irc.arcti.ca: YES
39 | irc.isprime.com: YES
40 | efnet.skynet.be: NO
41 | irc.wh.verio.net: YES
42 | irc.nac.net: YES
43 | irc.avalonworks.ca: YES
44 | irc.banetele.no: YES
45 | irc.dkom.at: YES
46 | irc.mpls.ca: YES
47 | irc.choopa.net: YES
48 | irc.foxlink.net: YES
49 |                                                                                 
50 | YES: 21
51 | NO: 1
52 | ABSTAIN: 1
53 |                                                                                 
54 | The following servers did not vote:
55 |                                                                                 
56 | irc.prison.net
57 | efnet.cs.hut.fi
58 | irc.limelight.us
59 | irc.homelien.no
60 | irc.csbnet.se
61 | irc-efnet.svc.us.xo.net
62 | irc.isdnet.fr
63 | irc.weblook2k.com
64 | irc.daxnet.no
65 | hub.se
66 | efnet.xs4all.nl
67 | irc.secsup.org
68 | irc.aol.com
69 | irc.inet.tele.dk
70 | irc.qeast.net
71 | irc.mindspring.com
72 | irc.aloha.net
73 | irc.desync.com
74 | irc.dks.ca
75 | 
76 | 77 |

78 | 79 | Click Here to go back.
80 | 81 | 82 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0036.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: no create on split
5 | Date of conclusion : 23 Aug 2003 6 | Result: PASSED (yes: 22, no: 2, abstain: 0) 7 |
8 | 9 | Description:

10 | 11 |
12 | The following vote has closed:
13 |                                                                                 
14 | no create on split
15 |                                                                                 
16 | This vote will require servers to use either
17 | NO_CREATE_ON_SPLIT or
18 | KICK_ON_SPLIT_RIDING.  The features solve the problem of
19 | people using
20 | splits to be able to get into +ik channels.
21 |                                                                                 
22 | Voting YES will require servers to use NO_CREATE_ON_SPLIT or
23 | KICK_ON_SPLIT_RIDING.  Implementation of this must take
24 | place within 4 weeks of the close of vote.
25 |                                                                                 
26 | Voting NO will not require servers to use these features.
27 |                                                                                 
28 | The results were as follows (summary at end):
29 |                                                                                 
30 | irc.dks.ca: YES
31 | efnet.xs4all.nl: YES
32 | efnet.demon.co.uk: YES
33 | irc.servercentral.net: YES
34 | irc.limelight.us: YES
35 | irc.blessed.net: YES
36 | irc.aloha.net: YES
37 | irc.efnet.nl: YES
38 | irc.efnet.pl: YES
39 | irc.easynews.com: YES
40 | irc.umn.edu: NO
41 | irc.weblook2k.com: YES
42 | ircd.lagged.org: YES
43 | irc.du.se: YES
44 | irc.he.net: YES
45 | irc.csbnet.se: YES
46 | irc.arcti.ca: YES
47 | irc.wh.verio.net: YES
48 | efnet.skynet.be: YES
49 | irc.mindspring.com: YES
50 | irc.banetele.no: NO
51 | irc.dkom.at: YES
52 | irc.choopa.net: YES
53 | irc.foxlink.net: YES
54 |                                                                                 
55 | YES: 22
56 | NO: 2
57 | ABSTAIN: 0
58 |                                                                                 
59 | The following servers did not vote:
60 |                                                                                 
61 | irc.umich.edu
62 | irc.prison.net
63 | efnet.cs.hut.fi
64 | irc.homelien.no
65 | irc.inter.net.il
66 | irc-efnet.svc.us.xo.net
67 | irc.isdnet.fr
68 | irc.daxnet.no
69 | hub.se
70 | irc.secsup.org
71 | irc.aol.com
72 | irc.inet.tele.dk
73 | irc.nac.net
74 | irc.avalonworks.ca
75 | irc.desync.com
76 | 
77 | 78 |

79 | 80 | Click Here to go back.
81 | 82 | 83 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0037.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: Hostname spoofing amendment
5 | Date of conclusion : 25 Aug 2003 6 | Result: PASSED (yes: 22, no: 3, abstain: 3) 7 |
8 | 9 | Description:

10 | 11 |
12 | The following vote has closed:
13 |                                                                                 
14 | Hostname spoofing amendment
15 |                                                                                 
16 | Spoofing hostnames/ips of clients used to control drones
17 | that only
18 | accept commands from a particular hostname/ip shall be
19 | allowed when
20 | used for the sole purpose of obtaining control of those
21 | drones in
22 | order to clean/disinfect those drones or to disable those
23 | drones.
24 |                                                                                 
25 |                                                                                 
26 | The results were as follows (summary at end):
27 |                                                                                 
28 | irc.dks.ca: YES
29 | efnet.xs4all.nl: YES
30 | irc.servercentral.net: YES
31 | efnet.demon.co.uk: YES
32 | irc.limelight.us: YES
33 | irc.blessed.net: YES
34 | irc.efnet.nl: YES
35 | irc.efnet.pl: YES
36 | irc.easynews.com: NO
37 | irc.umn.edu: NO
38 | irc.weblook2k.com: YES
39 | ircd.lagged.org: YES
40 | irc.du.se: YES
41 | irc.umich.edu: YES
42 | irc.he.net: YES
43 | irc.csbnet.se: YES
44 | irc.arcti.ca: YES
45 | efnet.skynet.be: ABSTAIN
46 | irc.wh.verio.net: ABSTAIN
47 | irc.nac.net: NO
48 | irc.mindspring.com: YES
49 | irc.secsup.org: YES
50 | irc.avalonworks.ca: YES
51 | irc.banetele.no: YES
52 | irc.isdnet.fr: YES
53 | irc.dkom.at: YES
54 | irc.choopa.net: ABSTAIN
55 | irc.foxlink.net: YES
56 |                                                                                 
57 | YES: 22
58 | NO: 3
59 | ABSTAIN: 3
60 |                                                                                 
61 | The following servers did not vote:
62 |                                                                                 
63 | irc.prison.net
64 | efnet.cs.hut.fi
65 | irc.homelien.no
66 | irc.inter.net.il
67 | irc-efnet.svc.us.xo.net
68 | irc.daxnet.no
69 | hub.se
70 | irc.aol.com
71 | irc.inet.tele.dk
72 | irc.aloha.net
73 | irc.desync.com
74 | 
75 | 76 |

77 | 78 | Click Here to go back.
79 | 80 | 81 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0039.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: Gline list addition: Flooding
5 | Date of conclusion : 12 Sep 2003 6 | Result: PASSED (yes: 18, no: 4, abstain: 3) 7 |
8 | 9 | Description:

10 | 11 |
12 | The following vote has closed:
13 |                                                                                 
14 | Gline list addition: Flooding
15 |                                                                                 
16 | This vote is to add flooding as an acceptable Gline
17 | reason.  Rather than defining a specific number of messages
18 | per minute or something similar, the definition of flooding
19 | will still be left to the discression of the opers placing
20 | the Gline.  However, let it be said that a client Glined
21 | for flooding must truly be disrupting network operations
22 | (again, at the discression of the 3 opers placing the
23 | Gline).
24 |                                                                                 
25 | The results were as follows (summary at end):
26 |                                                                                 
27 | efnet.xs4all.nl: NO
28 | efnet.demon.co.uk: NO
29 | irc.limelight.us: YES
30 | irc.blessed.net: YES
31 | irc.inter.net.il: YES
32 | irc.efnet.nl: YES
33 | irc.aloha.net: ABSTAIN
34 | irc.umn.edu: NO
35 | irc.efnet.pl: YES
36 | irc.easynews.com: NO
37 | irc.du.se: YES
38 | irc.he.net: YES
39 | irc.umich.edu: YES
40 | irc.arcti.ca: YES
41 | irc.csbnet.se: YES
42 | irc.wh.verio.net: ABSTAIN
43 | irc.nac.net: YES
44 | efnet.skynet.be: YES
45 | irc.mindspring.com: YES
46 | irc.avalonworks.ca: YES
47 | irc.banetele.no: YES
48 | irc.isdnet.fr: YES
49 | irc.choopa.net: YES
50 | irc.prison.net: ABSTAIN
51 | irc.foxlink.net: YES
52 |                                                                                 
53 | YES: 18
54 | NO: 4
55 | ABSTAIN: 3
56 |                                                                                 
57 | The following servers did not vote:
58 |                                                                                 
59 | efnet.cs.hut.fi
60 | ircd.lagged.org
61 | irc.homelien.no
62 | irc.servercentral.net
63 | irc-efnet.svc.us.xo.net
64 | irc.weblook2k.com
65 | irc.daxnet.no
66 | hub.se
67 | irc.secsup.org
68 | irc.aol.com
69 | irc.inet.tele.dk
70 | irc.dkom.at
71 | irc.desync.com
72 | irc.dks.ca
73 | 
74 | 75 |

76 | 77 | Click Here to go back.
78 | 79 | 80 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0040.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: Gline list addition: Spamming
5 | Date of conclusion : 12 Sep 2003 6 | Result: PASSED (yes: 20, no: 2, abstain: 2) 7 |
8 | 9 | Description:

10 | 11 |
12 | The following vote has closed:
13 |                                                                                 
14 | Gline list addition: Spamming
15 |                                                                                 
16 | This vote is to add spamming as an acceptable Gline reason.
17 |                                                                                 
18 | Admins may recommend pursuing other methods of dealing with
19 | spammers such as reporting them, adding channel bans,
20 | and/or klining them.  However, this vote will make it an
21 | acceptable Gline reason should 3 opers decide to Gline a
22 | spammer.
23 |                                                                                 
24 | The results were as follows (summary at end):
25 |                                                                                 
26 | efnet.xs4all.nl: YES
27 | efnet.demon.co.uk: NO
28 | irc.limelight.us: YES
29 | irc.blessed.net: YES
30 | irc.inter.net.il: YES
31 | irc.efnet.nl: YES
32 | irc.aloha.net: ABSTAIN
33 | irc.efnet.pl: YES
34 | irc.easynews.com: NO
35 | irc.umn.edu: YES
36 | irc.du.se: YES
37 | irc.he.net: YES
38 | irc.umich.edu: YES
39 | irc.csbnet.se: YES
40 | irc.wh.verio.net: ABSTAIN
41 | irc.nac.net: YES
42 | efnet.skynet.be: YES
43 | irc.mindspring.com: YES
44 | irc.avalonworks.ca: YES
45 | irc.banetele.no: YES
46 | irc.isdnet.fr: YES
47 | irc.choopa.net: YES
48 | irc.prison.net: YES
49 | irc.foxlink.net: YES
50 |                                                                                 
51 | YES: 20
52 | NO: 2
53 | ABSTAIN: 2
54 |                                                                                 
55 | The following servers did not vote:
56 |                                                                                 
57 | efnet.cs.hut.fi
58 | ircd.lagged.org
59 | irc.homelien.no
60 | irc.servercentral.net
61 | irc-efnet.svc.us.xo.net
62 | irc.weblook2k.com
63 | irc.daxnet.no
64 | irc.arcti.ca
65 | hub.se
66 | irc.secsup.org
67 | irc.aol.com
68 | irc.inet.tele.dk
69 | irc.dkom.at
70 | irc.desync.com
71 | irc.dks.ca
72 | 
73 | 74 |

75 | 76 | Click Here to go back.
77 | 78 | 79 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0041.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: Gline list addition: Distribution of trojans/viruses
5 | Date of conclusion : 12 Sep 2003 6 | Result: PASSED (yes: 23, no: 0, abstain: 2) 7 |
8 | 9 | Description:

10 | 11 |
12 | The following vote has closed:
13 |                                                                                 
14 | Gline list addition: Distribution of trojans/viruses
15 |                                                                                 
16 | This vote is to add distribution of trojans/viruses as an
17 | acceptable Gline reason.
18 |                                                                                 
19 | The results were as follows (summary at end):
20 |                                                                                 
21 | efnet.xs4all.nl: YES
22 | efnet.demon.co.uk: YES
23 | irc.limelight.us: YES
24 | irc.blessed.net: YES
25 | irc.inter.net.il: YES
26 | irc.efnet.nl: YES
27 | irc.aloha.net: ABSTAIN
28 | irc.efnet.pl: YES
29 | irc.easynews.com: YES
30 | irc.umn.edu: YES
31 | irc.du.se: YES
32 | irc.he.net: YES
33 | irc.umich.edu: YES
34 | irc.arcti.ca: YES
35 | irc.csbnet.se: YES
36 | irc.wh.verio.net: ABSTAIN
37 | efnet.skynet.be: YES
38 | irc.nac.net: YES
39 | irc.mindspring.com: YES
40 | irc.avalonworks.ca: YES
41 | irc.banetele.no: YES
42 | irc.isdnet.fr: YES
43 | irc.choopa.net: YES
44 | irc.prison.net: YES
45 | irc.foxlink.net: YES
46 |                                                                                 
47 | YES: 23
48 | NO: 0
49 | ABSTAIN: 2
50 |                                                                                 
51 | The following servers did not vote:
52 |                                                                                 
53 | efnet.cs.hut.fi
54 | ircd.lagged.org
55 | irc.homelien.no
56 | irc.servercentral.net
57 | irc-efnet.svc.us.xo.net
58 | irc.weblook2k.com
59 | irc.daxnet.no
60 | hub.se
61 | irc.secsup.org
62 | irc.aol.com
63 | irc.inet.tele.dk
64 | irc.dkom.at
65 | irc.desync.com
66 | irc.dks.ca
67 | 
68 | 69 |

70 | 71 | Click Here to go back.
72 | 73 | 74 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0042.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: Gline list addition: Drones
5 | Date of conclusion : 12 Sep 2003 6 | Result: PASSED (yes: 19, no: 2, abstain: 3) 7 |
8 | 9 | Description:

10 | 11 |
12 | The following vote has closed:
13 |                                                                                 
14 | Gline list addition: Drones
15 |                                                                                 
16 | This vote is to allow the Glining of drones.
17 |                                                                                 
18 | For the purpose of this Gline reason/vote, a client is
19 | considered a drone if it meets all of the following
20 | requirements:
21 |                                                                                 
22 | - IRC connection established from a system without the
23 | knowledge of a user of the system.
24 | - IRC connection established by a piece of trojan software
25 | with the primary purpose of flooding and/or participating
26 | in denial of service attacks.
27 |                                                                                 
28 | Therefore, this vote does not cover *every* illegitimate
29 | client connection established from a compromised system
30 | (hackers on bnc's, xdcc bots whose primary purpose is to
31 | distribute files, possibly others).  Some admins would like
32 | to see such clients Glined, and some would like to see them
33 | dealt with in other ways.  Thus, they should be handled
34 | under another list item/vote which any admin should feel
35 | free to call if so desired.
36 |                                                                                 
37 | The results were as follows (summary at end):
38 |                                                                                 
39 | efnet.xs4all.nl: YES
40 | efnet.demon.co.uk: NO
41 | irc.limelight.us: YES
42 | irc.blessed.net: YES
43 | irc.inter.net.il: YES
44 | irc.efnet.nl: YES
45 | irc.aloha.net: ABSTAIN
46 | irc.easynews.com: NO
47 | irc.efnet.pl: YES
48 | irc.umn.edu: YES
49 | irc.du.se: YES
50 | irc.he.net: YES
51 | irc.umich.edu: YES
52 | irc.csbnet.se: YES
53 | irc.wh.verio.net: ABSTAIN
54 | efnet.skynet.be: YES
55 | irc.nac.net: YES
56 | irc.mindspring.com: YES
57 | irc.avalonworks.ca: ABSTAIN
58 | irc.banetele.no: YES
59 | irc.isdnet.fr: YES
60 | irc.choopa.net: YES
61 | irc.prison.net: YES
62 | irc.foxlink.net: YES
63 |                                                                                 
64 | YES: 19
65 | NO: 2
66 | ABSTAIN: 3
67 |                                                                                 
68 | The following servers did not vote:
69 |                                                                                 
70 | efnet.cs.hut.fi
71 | ircd.lagged.org
72 | irc.homelien.no
73 | irc.servercentral.net
74 | irc-efnet.svc.us.xo.net
75 | irc.weblook2k.com
76 | irc.daxnet.no
77 | irc.arcti.ca
78 | hub.se
79 | irc.secsup.org
80 | irc.aol.com
81 | irc.inet.tele.dk
82 | irc.dkom.at
83 | irc.desync.com
84 | irc.dks.ca
85 | 
86 | 87 |

88 | 89 | Click Here to go back.
90 | 91 | 92 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0043.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
  4 | Topic: Acceptable Gline Usage
5 | Date of conclusion : 12 Sep 2003 6 | Result: PASSED (yes: 22, no: 1, abstain: 2) 7 |
8 | 9 | Description:

10 | 11 |
 12 | The following vote has closed:
 13 |                                                                                 
 14 | Acceptable Gline Usage
 15 |                                                                                 
 16 | Admins that choose to enable Glines give hundreds of opers
 17 | the ability to ban clients from their servers at the oper's
 18 | discression.  With the vast number of opers, requiring
 19 | two "seconds", without any guidelines as to what is
 20 | acceptable and what is not, is not effective in preventing
 21 | abuse.
 22 | 
 23 | Because the Gline acls admins can set in order to control
 24 | the circumstances in which Glines do/do not take affect on
 25 | their server are primitive at best (and this method is not
 26 | necessarily ideal even if the acls were not primitive), it
 27 | is only fair to expect that opers will only place Glines
 28 | for reasons that are accepted by *most* admins.
 29 |                                                                                 
 30 | Accordingly, this vote calls for the restriction of Glines
 31 | to be set only for reasons approved by the admin body.
 32 | Each reason must be voted on individually so admins need
 33 | not compromise at all.
 34 |                                                                                 
 35 | This vote, as always, supercedes all others previously
 36 | called where relevant.
 37 |                                                                                 
 38 | Note: I will be calling 4 other individual votes on
 39 | reasons.  Admins who would like to see additional reasons
 40 | should feel free to call their own votes as well.  (For
 41 | example, qurve mentioned a benefit in Glining drone runners
 42 | just before taking a drone channel over.  He could call
 43 | that vote...)
 44 | 
 45 |                                                                                 
 46 | The results were as follows (summary at end):
 47 |                                                                                 
 48 | efnet.xs4all.nl: YES
 49 | efnet.demon.co.uk: YES
 50 | irc.limelight.us: YES
 51 | irc.blessed.net: YES
 52 | irc.inter.net.il: YES
 53 | irc.aloha.net: ABSTAIN
 54 | irc.efnet.nl: YES
 55 | irc.efnet.pl: YES
 56 | irc.easynews.com: YES
 57 | irc.umn.edu: YES
 58 | irc.du.se: ABSTAIN
 59 | irc.he.net: YES
 60 | irc.umich.edu: YES
 61 | irc.arcti.ca: YES
 62 | irc.csbnet.se: YES
 63 | irc.wh.verio.net: NO
 64 | efnet.skynet.be: YES
 65 | irc.nac.net: YES
 66 | irc.mindspring.com: YES
 67 | irc.avalonworks.ca: YES
 68 | irc.banetele.no: YES
 69 | irc.isdnet.fr: YES
 70 | irc.choopa.net: YES
 71 | irc.foxlink.net: YES
 72 | irc.prison.net: YES
 73 |                                                                                 
 74 | YES: 22
 75 | NO: 1
 76 | ABSTAIN: 2
 77 |                                                                                 
 78 | The following servers did not vote:
 79 |                                                                                 
 80 | efnet.cs.hut.fi
 81 | ircd.lagged.org
 82 | irc.homelien.no
 83 | irc.servercentral.net
 84 | irc-efnet.svc.us.xo.net
 85 | irc.weblook2k.com
 86 | irc.daxnet.no
 87 | hub.se
 88 | irc.secsup.org
 89 | irc.aol.com
 90 | irc.inet.tele.dk
 91 | irc.dkom.at
 92 | irc.desync.com
 93 | irc.dks.ca
 94 | 
95 | 96 |

97 | 98 | Click Here to go back.
99 | 100 | 101 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0044.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: Gline list addition: Drone runner with restriction
5 | Date of conclusion : 23 Sep 2003 6 | Result: NOT PASSED (yes: 12, no: 3, abstain: 3) 7 | Note: Vote did not reach the quorum (insufficient votes) 8 |
9 | 10 | Description:

11 | 12 |
13 | The following vote has closed:
14 |                                                                                 
15 | Gline list addition: Drone runner with restriction
16 |                                                                                 
17 | This vote is to allow the Glining of drone runners
18 | immediately before taking control of a channel on which the
19 | drone runner's drones are controled.
20 |                                                                                 
21 | As with the other drone runners vote, this vote also gives
22 | drone runners their own category separate from "distributor
23 | of trojans/viruses".
24 |                                                                                 
25 | The results were as follows (summary at end):
26 |                                                                                 
27 | irc.limelight.us: YES
28 | efnet.skynet.be: YES
29 | irc.wh.verio.net: ABSTAIN
30 | irc.blessed.net: YES
31 | irc.nac.net: YES
32 | irc.mindspring.com: YES
33 | hub.se: NO
34 | irc.efnet.nl: YES
35 | irc.easynews.com: NO
36 | irc.umn.edu: NO
37 | irc.weblook2k.com: ABSTAIN
38 | ircd.lagged.org: ABSTAIN
39 | irc.du.se: YES
40 | irc.choopa.net: YES
41 | irc.prison.net: YES
42 | irc.foxlink.net: YES
43 | irc.umich.edu: YES
44 | irc.he.net: YES
45 |                                                                                 
46 | YES: 12
47 | NO: 3
48 | ABSTAIN: 3
49 |                                                                                 
50 | The following servers did not vote:
51 |                                                                                 
52 | efnet.cs.hut.fi
53 | irc.banetele.no
54 | irc.homelien.no
55 | irc.csbnet.se
56 | efnet.demon.co.uk
57 | irc.inter.net.il
58 | irc.servercentral.net
59 | irc-efnet.svc.us.xo.net
60 | irc.isdnet.fr
61 | irc.daxnet.no
62 | irc.arcti.ca
63 | efnet.xs4all.nl
64 | irc.secsup.org
65 | irc.aol.com
66 | irc.inet.tele.dk
67 | irc.efnet.pl
68 | irc.aloha.net
69 | irc.dkom.at
70 | irc.avalonworks.ca
71 | irc.desync.com
72 | irc.dks.ca
73 | 
74 | 75 |

76 | 77 | Click Here to go back.
78 | 79 | 80 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0045.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
 4 | Topic: Gline list addition: Drone runner with restriction (II)
5 | Date of conclusion : 29 Sep 2003 6 | Result: PASSED (yes: 25, no: 1, abstain: 3) 7 | Note: re-called, passed this time. 8 |
9 | 10 | Description:

11 | 12 |
13 | The following vote has closed:
14 |                                                                                 
15 | Gline list addition: Drone runner with restriction
16 |                                                                                 
17 | This vote is to allow the Glining of drone runners
18 | immediately before taking control of a channel on which the
19 | drone runner's drones are controled.
20 |                                                                                 
21 | As with the other drone runners vote, this vote also gives
22 | drone runners their own category separate from "distributor
23 | of trojans/viruses".
24 |                                                                                 
25 | The results were as follows (summary at end):
26 |                                                                                 
27 | irc.dks.ca: YES
28 | efnet.xs4all.nl: YES
29 | irc.limelight.us: YES
30 | efnet.demon.co.uk: YES
31 | irc.blessed.net: YES
32 | hub.se: ABSTAIN
33 | irc.aloha.net: YES
34 | irc.efnet.nl: YES
35 | irc.efnet.pl: YES
36 | irc.homelien.no: YES
37 | irc.easynews.com: NO
38 | irc.weblook2k.com: YES
39 | ircd.lagged.org: YES
40 | irc.du.se: YES
41 | irc.umich.edu: YES
42 | irc.he.net: YES
43 | irc.arcti.ca: YES
44 | irc.csbnet.se: YES
45 | efnet.skynet.be: YES
46 | irc.nac.net: YES
47 | irc.wh.verio.net: ABSTAIN
48 | irc.mindspring.com: YES
49 | irc.avalonworks.ca: YES
50 | irc.banetele.no: YES
51 | irc.isdnet.fr: YES
52 | irc.dkom.at: ABSTAIN
53 | irc.choopa.net: YES
54 | irc.daxnet.no: YES
55 | irc.foxlink.net: YES
56 |                                                                                 
57 | YES: 25
58 | NO: 1
59 | ABSTAIN: 3
60 |                                                                                 
61 | The following servers did not vote:
62 |                                                                                 
63 | irc.prison.net
64 | efnet.cs.hut.fi
65 | irc.inter.net.il
66 | irc.servercentral.net
67 | irc-efnet.svc.us.xo.net
68 | irc.umn.edu
69 | irc.secsup.org
70 | irc.aol.com
71 | irc.inet.tele.dk
72 | irc.desync.com
73 | 
74 | 75 |

76 | 77 | Click Here to go back.
78 | 79 | 80 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0046.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Addition to the acceptable gline policy
4 | Status: PASSED (yes:17 , no:4 , abstain:4 , elig: )

5 | 6 | Description:

7 | 8 |
  9 | 
 10 | G-line policies
 11 | 
 12 | This policy supersedes all previous G-line policies, with
 13 | the exception of the currently effective list of acceptable
 14 | G-line reasons, which should be used as the initial
 15 | 'acceptable' list defined by this document.
 16 | 
 17 | 
 18 | Definitions
 19 |   An 'oper' is any person with local G-line privileges on
 20 | any server
 21 |   An 'admin' is the person(s) listed on the voting interface
 22 | as representatives of a server, with a maximum of 3 admins
 23 | per server entity.
 24 |   A 'caller' is the person actually issuing an initial
 25 | G-line request
 26 |   A 'server entity' is any set of servers that is counted as
 27 | a single voting entity.
 28 |   A 'request' is the action of actually issuing the calling
 29 | and/or seconding G-line request.
 30 | 
 31 | 
 32 | Policy:
 33 | 
 34 | * Any G-line requires 3 requests, from 3 different persons
 35 | and 3 different server entities.
 36 | 
 37 | * Requests may only be issued from permanently linked servers.
 38 | 
 39 | * Trial servers and experimental/test servers must have
 40 | G-lines enabled.
 41 | 
 42 | * Two lists of unambigious G-line reasons will be
 43 | established by vote, one 'acceptable' and one
 44 | 'unacceptable'. The acceptable list will initially consist
 45 | of the currently agreed on acceptable g-line reasons.
 46 | 
 47 | * Any oper (and admin) may issue requests for any reason
 48 | given in the 'acceptable' list.
 49 | 
 50 | * Noone may issue requests for any reason given in the
 51 | 'unacceptable' list
 52 | 
 53 | * Any admin (not opers), may issue requests for reasons not
 54 | covered by either lists.
 55 | 
 56 | * It is the calling opers/admins responsibility to ensure
 57 | that the reason given in any called G-line is not misleading.
 58 | 
 59 | * It is the requesting opers/admins responsibility to ensure
 60 | that he/she does not second a G-line which would violate policy.
 61 | 
 62 | 
 63 | Enforcement:
 64 | 
 65 | * Failure to obey these policies will lead to immediate
 66 | removal of G-line privileges for the offending oper(s), for
 67 | a period of 3 months, starting no later than 1 week after
 68 | the offence. Repeated failure to obey these policies will
 69 | lead to a removal of G-line privileges for a period of 1
 70 | year, starting no later than 1 week after the repeated offence.
 71 | 
 72 | The results were as follows (summary at end):
 73 | 
 74 | irc.efnet.pl: YES
 75 | irc.blessed.net: ABSTAIN
 76 | irc.foxlink.net: YES
 77 | irc.homelien.no: YES
 78 | irc.easynews.com: NO
 79 | irc.dks.ca: YES
 80 | irc.umn.edu: YES
 81 | irc.inter.net.il: NO
 82 | irc.banetele.no: YES
 83 | irc.choopa.net: NO
 84 | irc.mzima.net: YES
 85 | irc.limelight.us: ABSTAIN
 86 | irc.nac.net: NO
 87 | irc.desync.com: ABSTAIN
 88 | irc.dkom.at: ABSTAIN
 89 | irc.avalonworks.ca: YES
 90 | irc.mindspring.com: YES
 91 | irc.he.net: YES
 92 | irc.daxnet.no: YES
 93 | irc.csbnet.se: YES
 94 | efnet.aixit.de: YES
 95 | efnet.demon.co.uk: YES
 96 | efnet.xs4all.nl: YES
 97 | irc.efnet.nl: YES
 98 | irc.du.se: YES
 99 | 
100 | YES: 17
101 | NO: 4
102 | ABSTAIN: 4
103 | 
104 | The following servers did not vote:
105 | 
106 | irc.umich.edu
107 | irc.prison.net
108 | efnet.cs.hut.fi
109 | ircd.lagged.org
110 | irc.servercentral.net
111 | irc.concentric.net
112 | irc.wh.verio.net
113 | irc.arcti.ca
114 | hub.se
115 | irc.secsup.org
116 | irc.inet.tele.dk
117 | 
118 | 

119 | 120 | Click Here to go back.
121 | 122 | 123 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0047.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: OCF test period
4 | Called by: (Salvation)
5 | Seconded by: (Disciple)
6 | Called on: 27/09/04
7 | Ended on: 12/10/i04
8 | Status: PASSED (yes: 18 , no: 4, abstain: 2, elig:35 )

9 | 10 | Description:

11 | 12 |
13 | 
14 | This vote is to grant services.eu admins a two week period
15 | to run OpenChanfix in full production. In order for this to
16 | happen, services.int admins will have to put Chanfix in data
17 | collection mode only. This vote by no means approves
18 | OpenChanfix as a replacement of Chanfix. The exact time
19 | frame is to be worked out with the admins of services.int
20 | and services.eu. The two week test period must happen before
21 | the end of 2004. After the two week test period, OpenChanfix
22 | must return back to data collection only mode and Chanfix to
23 | return to full production mode.
24 | 
25 | This two week test period may be canceled if the admins of
26 | services.eu and services.int collectively agree, due to any
27 | problem with OpenChanfix.
28 | 
29 | The results were as follows (summary at end):
30 | 
31 | irc.efnet.pl: YES
32 | irc.blessed.net: YES
33 | irc.foxlink.net: YES
34 | irc.easynews.com: NO
35 | ircd.lagged.org: NO
36 | irc.umn.edu: YES
37 | irc.inter.net.il: YES
38 | irc.concentric.net: ABSTAIN
39 | irc.banetele.no: NO
40 | irc.choopa.net: YES
41 | irc.mzima.net: YES
42 | irc.limelight.us: YES
43 | irc.nac.net: NO
44 | irc.scnet.net: YES
45 | irc.dkom.at: YES
46 | irc.avalonworks.ca: YES
47 | irc.dataphone.se: YES
48 | irc.inet.tele.dk: YES
49 | irc.mindspring.com: YES
50 | irc.wh.verio.net: ABSTAIN
51 | efnet.demon.co.uk: YES
52 | efnet.xs4all.nl: YES
53 | irc.du.se: YES
54 | irc.efnet.nl: YES
55 | 
56 | YES: 18
57 | NO: 4
58 | ABSTAIN: 2
59 | 
60 | The following servers did not vote:
61 | 
62 | irc.umich.edu
63 | irc.prison.net
64 | efnet.cs.hut.fi
65 | irc.homelien.no
66 | irc.kagmir.ca
67 | irc.daxnet.no
68 | irc.arcti.ca
69 | irc.he.net
70 | hub.se
71 | irc.desync.com
72 | irc.dks.ca
73 | 
74 | 
75 | 
76 | 
77 | 
78 | 
79 | 80 |

81 | 82 | Click Here to go back.
83 | 84 | 85 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0048.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: Global gline requirement
4 | Called by: (Hardy)
5 | Seconded by: (ik)
6 | Called on: 26/01/05
7 | Ended on: 10/02/05
8 | Status: PASSED (yes: 18 , no: 10, abstain: 3, elig:35 )

9 | 10 | Description:

11 | 12 |
13 | 
14 | Global gline requirement
15 | 
16 | This vote will require all servers on EFnet to have glines
17 | enabled. The gline expiration time may be decided by
18 | individual servers, but it can not be less than 6 hours, or
19 | more than 7 days.
20 | 
21 | If the vote is approved, all servers will be required to
22 | activate glines within a 14 day period. The 14 days will
23 | begin on the day this vote closes. Failure to comply will
24 | result in the server(s) being removed from the network.
25 | 
26 | If the vote do not pass, it will not affect the european
27 | regional rule on gline requirement.
28 | 
29 | The results were as follows (summary at end):
30 | 
31 | irc.efnet.pl: YES
32 | irc.arcti.ca: YES
33 | irc.blessed.net: YES
34 | irc.homelien.no: NO
35 | irc.easynews.com: NO
36 | irc.dks.ca: YES
37 | ircd.lagged.org: NO
38 | irc.umn.edu: NO
39 | irc.umich.edu: NO
40 | irc.inter.net.il: ABSTAIN
41 | irc.banetele.no: YES
42 | irc.choopa.net: NO
43 | irc.mzima.net: YES
44 | irc.nac.net: NO
45 | irc.scnet.net: YES
46 | irc.desync.com: YES
47 | irc.dkom.at: YES
48 | irc.avalonworks.ca: YES
49 | irc.dataphone.se: YES
50 | irc.inet.tele.dk: YES
51 | irc.mindspring.com: YES
52 | irc.he.net: YES
53 | irc.daxnet.no: YES
54 | irc.colosolutions.net: NO
55 | efnet.xs4all.nl: ABSTAIN
56 | irc.kagmir.ca: YES
57 | efnet.demon.co.uk: NO
58 | irc.du.se: YES
59 | irc.efnet.nl: YES
60 | irc.prison.net: NO
61 | hub.se: ABSTAIN
62 | 
63 | YES: 18
64 | NO: 10
65 | ABSTAIN: 3
66 | 
67 | The following servers did not vote:
68 | 
69 | efnet.cs.hut.fi
70 | irc.limelight.us
71 | irc.concentric.net
72 | irc.wh.verio.net
73 | 
74 | 
75 | 
76 | 
77 | 
78 | 
79 | 80 |

81 | 82 | Click Here to go back.
83 | 84 | 85 | -------------------------------------------------------------------------------- /misc/voting.efnet.org/archives/0049.shtml: -------------------------------------------------------------------------------- 1 | 2 | 3 | Topic: services.int reorganization/replacement of chanfix
4 | Called by: (Fraggle)
5 | Seconded by: (Disciple)
6 | Called on: 22/04/05
7 | Ended on: 07/05/05
8 | Status: PASSED (yes: 25 , no: 1, abstain: 5, elig:35 )

9 | 10 | Description:

11 | 12 |
 13 | 
 14 | services.int reorganization/replacement of chanfix
 15 | 
 16 | This vote will ultimately lead to the creation of one
 17 | centralized services, and one set of backup services.
 18 | Openchanfix has proven itself stable, has been ported to
 19 | ratbox2, and by the time this vote comes to a
 20 | conclusion be ready to go into full production mode.
 21 | 
 22 | If this vote passes, open chanfix (OCF) will replace the
 23 | current code running on services.int. Garion (as a
 24 | representative from the coding team) plus a representative
 25 | nominated and elected by each region will form the new
 26 | group of services admins responsible for maintaining and
 27 | operating the new services.int. These elected
 28 | representatives, and Garion as representative of the
 29 | coding team, will then assume full responsibility for
 30 | maintaining all services related matters. This includes
 31 | replacing JUPES with an actually operational
 32 | OpenJupes code (when ported to rb2) and any future
 33 | developments requested by the admin community as a whole.
 34 | 
 35 | A backup set of services will be run from the current
 36 | services.eu location, but be renamed backup.services.int.
 37 | It will run in passive mode incase of extended failure by
 38 | services.int.
 39 | 
 40 | thanks,
 41 | andrew
 42 | irc.easynews.com
 43 | 
 44 | 
 45 | The results were as follows (summary at end):
 46 | 
 47 | irc.efnet.pl: YES
 48 | irc.blessed.net: YES
 49 | irc.easynews.com: YES
 50 | efnet.port80.se: YES
 51 | irc.dks.ca: YES
 52 | irc.umich.edu: YES
 53 | irc.umn.edu: YES
 54 | irc.inter.net.il: YES
 55 | irc.igs.ca: YES
 56 | irc.banetele.no: NO
 57 | irc.choopa.net: YES
 58 | irc.limelight.us: YES
 59 | irc.mzima.net: YES
 60 | irc.scnet.net: YES
 61 | irc.desync.com: ABSTAIN
 62 | irc.dkom.at: ABSTAIN
 63 | irc.dataphone.se: YES
 64 | irc.inet.tele.dk: YES
 65 | irc.mindspring.com: YES
 66 | irc.he.net: YES
 67 | irc.colosolutions.net: YES
 68 | efnet.cs.hut.fi: YES
 69 | irc.wh.verio.net: YES
 70 | efnet.xs4all.nl: YES
 71 | efnet.demon.co.uk: YES
 72 | irc.kagmir.ca: YES
 73 | irc.du.se: YES
 74 | irc.prison.net: YES
 75 | irc.efnet.nl: ABSTAIN
 76 | hub.se: ABSTAIN
 77 | 
 78 | YES: 25
 79 | NO: 1
 80 | ABSTAIN: 4
 81 | 
 82 | The following servers did not vote:
 83 | 
 84 | ircd.lagged.org
 85 | irc.homelien.no
 86 | irc.concentric.net
 87 | irc.daxnet.no
 88 | irc.arcti.ca
 89 | irc.nac.net
 90 | 
 91 | 
 92 | 
 93 | 
 94 | 
 95 | 
96 | 97 |

98 | 99 | Click Here to go back.
100 | 101 | 102 | -------------------------------------------------------------------------------- /server/SOURCE: -------------------------------------------------------------------------------- 1 | espel-tsora/Undernet-TS.txt http://web.archive.org/web/20110831120432/http://www.iagora.com/~espel/ircd/Undernet-TS 2 | espel-tsora/announcement.txt http://web.archive.org/web/20081015172856/http://www.iagora.com/~espel/ircd/announcement 3 | espel-tsora/index.html http://web.archive.org/web/20091202102553/http://www.iagora.com/~espel/ircd/index.html 4 | espel-tsora/lets-do-TS.txt http://web.archive.org/web/20080820034739/http://www.iagora.com/~espel/ircd/lets-do-TS 5 | espel-tsora/protocol.html http://web.archive.org/web/20120404102711/http://www.iagora.com/~espel/ircd/protocol.html 6 | p10-beware.txt http://ircd.bircd.org/bewarep10.txt 7 | ts1.txt ftp://quatramaran.ens.fr/pub/orabidoo/ircd/old/irc2.8.21%2BTSora.tar.gz::README.TSora 8 | ts3.txt ftp://quatramaran.ens.fr/pub/orabidoo/ircd/README.TS3 9 | ts4-faq.txt ftp://quatramaran.ens.fr/pub/orabidoo/ircd/TS4-dev/TS4.FAQ 10 | ts4.txt ftp://quatramaran.ens.fr/pub/orabidoo/ircd/TS4-dev/README.TS4 11 | ts6-ufnc.txt https://github.com/freenode/ircd-seven/blob/ufnc/doc/technical/ufnc.txt 12 | -------------------------------------------------------------------------------- /server/espel-tsora/lets-do-TS.txt: -------------------------------------------------------------------------------- 1 | Return-Path: 2 | Resent-Date: Tue, 5 Dec 1995 12:07:20 -0500 (EST) 3 | Subject: LETS DO TS 4 | To: operlist@kei.com, irc-eu@grasp.insa-lyon.fr 5 | Date: Tue, 5 Dec 1995 09:05:34 -0800 (PST) 6 | Resent-Message-Id: <"gLRt43.0.2o5.7n7nm"@kei.com> 7 | Resent-From: operlist@kei.com 8 | X-Mailing-List: archive/latest/216 9 | X-Loop: operlist@kei.com 10 | Precedence: list 11 | Resent-Sender: operlist-request@kei.com 12 | 13 | 14 | Ok people.. after ruffling everyone's feathers, I have decided to take 15 | down the channel.un service (the UN bot will go back to being a normal 16 | channel bot as it was before). The results of "voting" were in favor 17 | of a channel-service, those who voted against one were out numbered. 18 | 19 | I have taken the service down because I think TS is a better solution 20 | to our problems. I hope we don't need to vote on whether to use 21 | TS or not. 22 | 23 | Can we make a TS (patch) that is compatible with non-TS servers? I'd 24 | like to see something on the table within the next few weeks at least. 25 | 26 | If people are going to sit on their butts again and let this thing 27 | go without doing anything, I will consider bringing the channel 28 | service back up since a majority of those who voted were for it. I'd 29 | rather not do this, I'd rather see TS. 30 | 31 | Those wanting to help with the move to TS, please subscribe to the 32 | emailing ircd2-patches@kei.com by emailing ircd2-patches-request@kei.com 33 | with the word SUBSCRIBE in the subject of the message. We need people 34 | who will code the patches and people who will help plan the installation 35 | and MOVE. 36 | 37 | Thanks to the numerous people who supported my efforts by letting me 38 | know in private email, I appreciate it and am glad to see that I'm not 39 | the only one who is sick of trying to operate a broken protocol. 40 | 41 | LET'S DO IT! TS IS COMING! TS IS COMING! 42 | 43 | -- 44 | Damon M. Pike (piker) [UN-Net/UIRC/*.portal.com IRC Administrator] 45 | ---------------------------------------------------------------------- 46 | Email: piker@shell.portal.com WWW: http://www.portal.com/~piker 47 | ---------------------------------------------------------------------- 48 | - United Internet Relay Chatters - Email: uirc@shell.portal.com 49 | - UN-Net Emergency/News hub on /server irc.portal.com 9111 50 | ---------------------------------------------------------------------- 51 | NOTE: Comments/opinions expressed are Piker's unless otherwise noted. 52 | 53 | -------------------------------------------------------------------------------- /server/p10-login-on-connect.txt: -------------------------------------------------------------------------------- 1 | Login-on-connect documentation 2 | Last updated 22 Jun 2004 by Vampire- 3 | 4 | 1. This feature is experimental. 5 | 6 | 2. The main point is to allow clients to log in to a service bot (i.e., X) 7 | *before* being announced to the network. Otherwise, a combination of a 8 | malicious user, /ISON, /USERIP and low latency can reveal it's real host/IP 9 | before he gets a chance to log in and set himself +x 10 | 11 | 3. Client<->Server changes: 12 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ 13 | The PASS command now has the following syntax: 14 | 15 | PASS [optional I-line password] : 16 | 17 | If the client sends such a password message, after sending NICK, 18 | USER and PONG, it's username/passphrase are sent to the specified bot 19 | for validation, while holding the client in the 'registration' state. 20 | If the authentication succeeds, the client's account and umode +x are set, 21 | after which he is introduced to the network, continuing the regular connect 22 | phase. If authentication fails (or the bot is not on the network), the user 23 | is given a chance to retry (he can do this by sending another PASS command), 24 | or to disconnect from the server. If he wishes to connect without a hidden 25 | hostmask, he can send a PASS command with no parameters. 26 | 27 | Update: For buggy clients that send ("PASS :%s", whatever-the-user-typed) 28 | and thus are incapable of sending multiple arguments, there's a hack in 29 | mr_pass that splits up the argument if the first character is a ':'. 30 | This way users might use ":bot user :pass phrase" in their clients. 31 | The example above would be, in raw form: 32 | 33 | PASS ::[optional I-line password] : 34 | 35 | 4. Server<->Server changes: 36 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ 37 | The ACCOUNT message now has the following syntax: 38 | 39 | Auth check: 40 | AC C : 41 | Servers send this message to request a service bot to authenticate the client. 42 | is not processed neither by the servers along the way nor the 43 | service bot. Currently this is: 44 | '.' '.' 45 | The inital '.' makes sure that the ID is not a valid integer, which is part of 46 | the hack required to support old-style ACCOUNT messages. The cookie is used to 47 | validate replies, since the user might disconnect and the fd be reused before 48 | the reply comes back from the service. Hubs propagate this message as-is 49 | towards the service bot, not unlike PRIVMSG. 50 | 51 | Auth reply: 52 | AC A|D 53 | Service bots send this in reply to an 'auth check' message from a server. 54 | "A" stands for "accepted", "D" for "denied". Again, hubs will have 55 | to proagate this message back to the client's server. 56 | 57 | Remote auth: 58 | AC R [] 59 | This is the current message used by service bots to announce the network 60 | that a user has logged in. The old format is still supported: 61 | AC [] 62 | 63 | 5. ircu code changes 64 | ~~~~~~~~~~~~~~~~~~~~ 65 | A new feature, FEAT_LOGIN_ON_CONNECT (default FALSE) will specify whether 66 | ircu will honour the login scheme as specified above for the PASS command. 67 | ircu will route ACCOUNT messages anyway, regardless of this feature's value. 68 | 69 | -------------------------------------------------------------------------------- /server/ts-capab.txt: -------------------------------------------------------------------------------- 1 | Server capabilities 2 | William Pitcock 3 | ------------------- 4 | 5 | Not all TSora IRCd's support these. 6 | 7 | QS - supports Quit Storm (SQUIT does not have to send recursive quits) 8 | EX - supports ban exceptions (+e) 9 | CHW - supports messages directed to channel operators only i.e. @#channel 10 | IE - supports invite exceptions (+I) 11 | EOB - supports end of burst notification (EOB token) 12 | KLN - supports remote KLINE 13 | UNKLN - supports remote UNKLINE 14 | GLN - supports hybrid7-style GLINE (:oper GLINE user host :reason) 15 | HOPS - supports halfops (+h -- %) 16 | HUB - denotes that the target server is a HUB 17 | AOPS - supports anonymous ops (+a, op hiding/op status hiding) 18 | KNOCK - supports KNOCK extension (request invite to +ikl channel) 19 | TBURST - supports old TBURST command [broken, don't use.] 20 | TB - supports new TB command [do use.] 21 | PARA - supports sending invite notices via INVITE from server 22 | ENCAP - supports message encapsulation 23 | SERVICES - supports ratbox's services extensions 24 | SAVE - supports SAVE extension (friendlier alternative to KILL on nick collide) 25 | RSFNC - supports RSFNC extension (forcenick) 26 | CLUSTER - supports remote XLINE, UNXLINE, RESV, UNRESV and LOCOPS 27 | EUID - supports EUID, non-ENCAP CHGHOST and NICKDELAY 28 | ZIP - supports ziplinks 29 | ENC - supports encryption (cryptlinks) 30 | 31 | The KLN, UNKLN and CLUSTER capabilities do not apply to klines, xlines 32 | and resvs sent over ENCAP. 33 | 34 | Disabling ban/invite exceptions in ircd.conf does not remove the EX/IE capabs. 35 | -------------------------------------------------------------------------------- /server/ts-encap.txt: -------------------------------------------------------------------------------- 1 | ENCAP DEFINITION 2 | ---------------- 3 | 4 | Preamble 5 | -------- 6 | 7 | This document defines the specification for the ENCAP command. 8 | 9 | ENCAP is designed to help fix the situation where new commands do 10 | not propagate over hub servers running older code. 11 | 12 | Definition 13 | ---------- 14 | 15 | Support for the ENCAP command is given by the CAPAB token "ENCAP". 16 | 17 | The format of ENCAP is: 18 | : ENCAP 19 | 20 | - The entity generating the command. 21 | 22 | - The entity the command is destined for. This may 23 | include wildcards for servers, but not clients. 24 | 25 | If the wildcard does not match the current server, the 26 | command should be propagated and ignored. 27 | 28 | - The subcommand we're propagating over ENCAP. If the 29 | subcommand is not recognised by the current server, the 30 | command should be propagated and ignored. 31 | 32 | - The parameters that the subcommand have. 33 | 34 | 35 | 36 | -------------------------------------------------------------------------------- /server/ts-kln-unkln-cluster.txt: -------------------------------------------------------------------------------- 1 | Short description of how remote kline and friends are propagated under 2 | the old hyb7 style (CAP_KLN etc) and under the new style over ENCAP. 3 | 4 | CAP_KLN: 5 | : KLINE