View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001462 | unreal | ircd | public | 2003-12-30 23:06 | 2003-12-31 04:50 |
| Reporter | x64 | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta19 | ||||
| Summary | 0001462: "~" is not a good choice for +q | ||||
| Description | Reasons: 1. ~ should technically (even mentioned in the src) be allowed in nicknames, and some ircd's do allow this. 2. +q is already known to most people as '.' and was one of the first non-rfc prefixes to be built into mirc (long before PREFIX=) to accomodate ircx and custom servers. 3. Even though some clients don't support PREFIX=, they still recognize +q as being '.' (from the dweeby ircx era). 4. ~ is used to already mean other things (no identd, secret channel, etc) 5. By moving the ~ prefix from secret to owner, you're forcing most of the oper's scripts to update. 6. Since ~ is still used on servers that don't have PREFIX_AQ set as secret, it forces scripts to actually check to not only see if +q is "~", but to see if the ircd version is actually Unreal or something else that might be using the prefix for some other reason. 7. It just looks wrong to me. | ||||
| 3rd party modules | |||||
|
|
1. ~ should technically (even mentioned in the src) be allowed in nicknames, and some ircd's do allow this. Your point? It's not allowed as the first character, and that's all that matters. 2. +q is already known to most people as '.' and was one of the first non-rfc prefixes to be built into mirc (long before PREFIX=) to accomodate ircx and custom servers. This is IRC, not IRCX. If clients have chosen to assume +q is a '.' just because that's what IRCX does, that's their problem, not ours. 3. Even though some clients don't support PREFIX=, they still recognize +q as being '.' (from the dweeby ircx era). Again, not our problem. 4. ~ is used to already mean other things (no identd, secret channel, etc) Yeah and? +, on some IRCds, is a type of channel, no conflicts there, + is also used to indicate a mode change. @ is used as part of a hostmask. 5. By moving the ~ prefix from secret to owner, you're forcing most of the oper's scripts to update. Ok, then they update. 6. Since ~ is still used on servers that don't have PREFIX_AQ set as secret, it forces scripts to actually check to not only see if +q is "~", but to see if the ircd version is actually Unreal or something else that might be using the prefix for some other reason. It requires NO such thing, it requires them to check what the value of PREFIX= is. 7. It just looks wrong to me. and . looks even stupider. In a non-fixed-width font it looks ridiculous. You bring up some valid points, but here is the thing. You're points are based on supposition. I've tested this in numerous clients. I didn't see a single client that automatically assumed +q meant . and any client that supports PREFIX= correctly works with Unreal. The bottom line, it's not going to be changed. |
|
|
1. What is IRC? IRC a protocol that Codemastr just takes it upon himself to update whenever his ideas see fit without consulting anyone but the people in his own dream world. 2. What is a steel baseball bat? A steel baseball bat is what people play baseball with. It is a very hard, very dense object that is very powerful once set into motion. 3. What is codemastr's cranium? A not-so-dense object that only expresses its own close-mindedness and stubborn views to the world. Codemastr knows that his life is not fulfilled because he can't express anything but his dire insecurity of other people's ideas that have succeeded in the past. Press "1" if you wish for object 3 to influence the commuinity established around object 1. Or press "2" if you wish for object 2 to be swung at object 3 at very high speeds. Or, if you are not calling from a touch tone phone, stay on the line for more options. edited on: 12-31-03 01:28 |
|
|
x64, If a client doesn't support 005/PREFIX= .. then in this day, its out of date. btw, point making that everything should be like IRCX is really stupid... no IRCd is perfect ps. the joke sucked. |
|
|
x64, thank you for your childish comments, bye! |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-12-30 23:06 | x64 | New Issue | |
| 2003-12-30 23:51 |
|
Note Added: 0004475 | |
| 2003-12-31 01:26 | x64 | Note Added: 0004478 | |
| 2003-12-31 01:28 | x64 | Note Edited: 0004478 | |
| 2003-12-31 03:23 | Praetorian_ | Note Added: 0004480 | |
| 2003-12-31 04:50 |
|
Status | new => closed |
| 2003-12-31 04:50 |
|
Note Added: 0004482 |
