-
Notifications
You must be signed in to change notification settings - Fork 19
/
Copy pathchanmembers.yaml
144 lines (129 loc) · 4.41 KB
/
chanmembers.yaml
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
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
# chanmembers.yaml
#
# This file is Copyright (c) 2015-2019 Daniel Oaks
# <daniel@danieloaks.net>
# This file is Copyright (c) 2001-2004 Simon Butcher
# <pickle@alien.net.au>
#
# This file is PUBLIC DOMAIN, to benefit the IRC developer community. If you
# modify this file, please state your name and modifications here in order
# for people to be able to distinguish between your version and this version.
#
# For more information or corrections, please contact the author.
file:
type: "chanmembers"
revision: "1.60"
# The following information is used to create pretty HTML page and tables
page:
name: Channel Member Prefixes
extra: >
<p>
Red denotes a conflicting numeric definition, gray for deprecated
(however quite possibly still in use), and blue for OK. Where
multiple prefix or mode characters may be commonly seen in the wild
for this membership prefix, they are listed together.
</p>
table:
row-id: name
row-classes:
- conflict
- obsolete
columns:
-
name: Prefix
content: prefixchar
classes: code center
inline-link: name
description: Prefix character
-
name: Name
content: name
classes: code
link: information
-
name: Mode
content: mode
classes: code center
description: Mode character that enables this prefix
-
name: Origin
content: origin
link: contact
description: Where the prefix came from
-
name: Comments
content: comment
seealso: seealso
description: "Additional comments, history and other details"
# The following format is used through-out this file. The fields 'name',
# 'prefixchar', and irc2_mode are mandatory, the others may or may not exist.
format:
name: membership type name
prefixchar: the prefix character for nicknames to denote status
mode: irc2 mode character associated with this membership
origin: where the mode was found
when: release version or announced date
contact: point of contact associated with the membership
information: url where to find more information
comment: "comments, history etc"
conflict: true
obsolete: true
values:
-
name: FOUNDER
prefixchar: "~"
mode: q
origin: EliteIRCd
comment: >
User created the channel. This user usually cannot be kicked
or have this mode taken away by other users. In some software,
they may perform actions that operators can, but are at a
higher privilege level than either operators or protected
users.
-
name: PROTECTED
prefixchar: "& !"
mode: a
origin: EliteIRCd
comment: >
User is "protected". This means they cannot be kicked or have
this mode taken away by operators (or other protected users).
In some software, they may perform actions that operators can,
but at a higher privilege level than operators.
-
name: OPERATOR
prefixchar: "@"
mode: o
origin: RFC1459
comment: >
User is a channel operator. They can kick users, change modes,
set other users to operator (or lower) status, etc.
-
name: HALF_OPERATOR
prefixchar: "%"
mode: h
origin: Hybrid
comment: >
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.
-
name: VOICED
prefixchar: "+"
mode: v
origin: RFC1459
comment: >
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)
-
name: CREATOR
prefixchar: "@"
mode: O
origin: RFC2811
comment: >
The user created the channel, but only used for '!' channels
according to the RFC.
obsolete: true