]>
Commit | Line | Data |
---|---|---|
1 | ||
2 | Date: Thu, 30 Jul 1998 16:21:40-0700 (MST) | |
3 | To: operlist@the-project.org | |
4 | From: rayp@primenet.com (Ray Powers) | |
5 | Subject: The myths of opers.... | |
6 | ||
7 | I've always wanted to write something like this.. Its half rant, half | |
8 | fact, so bear with it. Hopefully it will be worth reading. | |
9 | ||
10 | There's a lot of hate for opers for a lot of reasons. Some are directly | |
11 | oper related (i.e. 99% of us are colossal assholes), some are directly | |
12 | user related (i.e. 99% of you are raving lunatics), and some is just plain | |
13 | misconceptions. I'd like to take a minute to talk about part three in | |
14 | hopes of clearing a few things up. This will kind of be in a FAQ form, | |
15 | maybe you'll like it, maybe not, but its worth a shot. | |
16 | ||
17 | Q: What can an oper on EFnet do. | |
18 | A: This is an EXACT list of what we can do: | |
19 | 1) /squit a server, separating it from the rest of the net | |
20 | 2) /die our server | |
21 | 3) /kill a user, this disconnects them from the server they are on | |
22 | 4) /kline a hostmask, this bans them from our server | |
23 | 5) /dline an ip, this bans them from our server, regardless of | |
24 | hostmask | |
25 | 6) See all invisible users on our server | |
26 | 7) Mass Msg/CTCP/notice a hostmask | |
27 | 8) Mass Msg/CTCP/notice a server | |
28 | 9) See and send Operwall/wallops notices | |
29 | ||
30 | That's it. We can see more server messages than you, but that's not the | |
31 | point.. The point to be shown here is very simple, *none* of these things | |
32 | have anything to do with channels. Which leads us to our next question. | |
33 | ||
34 | Q: What can opers *NOT* do, but keep being asked to anyways? | |
35 | A: We can *NOT*: | |
36 | 1) Enter a channel that is +i or +k without being invited or | |
37 | having the key | |
38 | 2) See who is inside a +s channel | |
39 | 3) Op ourselves or op you on a channel (unless of course we are a | |
40 | channel op for that channel) | |
41 | 4) Tell you what XXXX's new nick is since they changed it to hide | |
42 | from you. | |
43 | 5) Deop someone for you on a channel (unless of course we are a | |
44 | channel op for that channel) | |
45 | ||
46 | Notice a trend, with the exception of 4, all of these are 100% channel | |
47 | related. EFnet is made so that opers have *NO* power of channels, for | |
48 | better or worse. If we don't help you with these requests, its not because | |
49 | we won't, its because we are completely incapable doing so. On the other | |
50 | hand.... | |
51 | ||
52 | Q: What can opers do, but won't? | |
53 | A: This will be a bit differently done, because I figure I should explain | |
54 | why opers don't do these things, when they may normally make sense. | |
55 | 1) Why won't they kill somebody who has stolen your nick. | |
56 | EFnet has gone on the basis of nicks not being owned, which is | |
57 | why there is no nickserv on EFnet. Of course we see opers kill | |
58 | all the time for nicks, though, so it seems rather hypocrital, | |
59 | doesn't it? | |
60 | An oper who kills for his nick will tell you its because the | |
61 | other person was a bot, was juping his nick, or was imitating an | |
62 | oper. It may be true, but it really comes down to the same | |
63 | feeling you get when your nick is taken "Hey! that's my name! I | |
64 | don't want that person using my name!" | |
65 | I personally, do not kill for nicks. If someone takes my nick, | |
66 | they can have it. Let them get my several hundred messages a day. | |
67 | :P But the problem with the oper is this: How does an oper know | |
68 | that you are really the person that uses that nick, or are you | |
69 | the guy that wants to nick jupe that nick out from the real guy? | |
70 | Unless the oper knows you well, they don't.. And saying that | |
71 | people generally tell the truth means you haven't been on EFnet | |
72 | very long. | |
73 | I would prefer to think I am one of the more well respected | |
74 | people on the net and people still lie to me on a regular basis. | |
75 | So, the oper is stuck refusing to help because he can't tell who | |
76 | is who. Remember this line of reasoning, its going to be coming | |
77 | up a lot. :P | |
78 | 2) Why won't they kill that guy nuking/smurfing/ping -f'ing me? | |
79 | This one is simple. There is no way to prove that somebody is | |
80 | doing any of these things to you from an opers point of view. All | |
81 | logs are fakeable, and the oper has no way to firsthand prove its | |
82 | happening. Your best bet in this situation is to log what you can | |
83 | and complain loud and long to their ISPs. | |
84 | 3) Why won't they help me take my channel back? | |
85 | There's a bunch of answers to this. First, it is popular | |
86 | opinion at EFnet that channels are not owned, and therefore, if | |
87 | you lose a channel, you should go make another one. Notice I | |
88 | say popular instead of official, because EFnet has never had an | |
89 | "official" policy on much of anything. | |
90 | But more and more you see opers killing for takeovers, so why | |
91 | are they helping their channels and not yours. | |
92 | Well, first, let's say your channel was taken over, and is now | |
93 | +smtinlk. How exactly is the oper supposed to find out who is | |
94 | oped in the channel right now to mass kill them? Even if they do get | |
95 | all the nicks, they have to somehow manage to kill them all in | |
96 | one hit, or they'll all just op each other again and it will be | |
97 | fruitless. Or worse, they could have it all set up, and some | |
98 | other oper could kill them halfway through because they don't | |
99 | like mass-kills and it would be all ruined. | |
100 | Or, let's say the mass-kill goes off, then the channel is | |
101 | opless and generally speaking, chaos begins. People start | |
102 | mass-nuking or flooding the channel to clear it out, or just to | |
103 | be annoying. And there's still a 50/50 chance that takeover | |
104 | people will get the channel back on a split and we'll have to try | |
105 | to do it all over again. | |
106 | If you're about to ask why they don't split their server, | |
107 | the answer is very simple: We are not about to screw up roughly | |
108 | 30,000 peoples chatting for your channel. Its rude. This of | |
109 | course is all based on the fact that we can prove its taken over, | |
110 | as per the conversation about nicks, we often can't. | |
111 | 4) But.. its obvious they took it from me! The topic says | |
112 | "Ha ha, we took your channel Rick!" for Pete's sake! And | |
113 | there's only One op, so you can kill him and get the channel | |
114 | back immediately! | |
115 | This one is a bit more complex, but its really a personal | |
116 | call. That one op could be a rampant smurfpup with a penis so | |
117 | tiny he has no choice but to rampantly smurf and synflood anyone | |
118 | that gets in his way. This is popularly known on irc as SPS, or | |
119 | Small Penis Syndrome. In this case, if the oper does help you | |
120 | out, they could end up with their server being downed for a day | |
121 | or two, and it really isn't worth it for your channel, no | |
122 | offense. | |
123 | ||
124 | Keep in mind that this is all spoken from the perspective of someone who | |
125 | *DOES* help with channels when possible, but understands greatly the | |
126 | reasons not to, and judges each situation very carefully. | |
127 | ||
128 | That's the gist of the information I was trying to get across. If you | |
129 | were cluefull enough to get on operlist, a lot of this may be common | |
130 | knowledge to you, but sometimes its good to step back and see why opers do | |
131 | what they do a lot of the time. | |
132 | ||
133 | Hoping this is of value to SOMEONE.... | |
134 | ||
135 | Ray Powers | |
136 | Monkster/MimePunk/PrimeMonk/PacMonk/MtgMonk/Ihavefartoomanynickstonickjupe | |
137 |