View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002324 | unreal | ircd | public | 2005-02-08 17:30 | 2005-02-19 14:25 |
| Reporter | fez | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Platform | x86 | OS | Linux | OS Version | 2.4.x |
| Summary | 0002324: option to make /list default to >3 | ||||
| Description | I think there should be a config option to allow for default /LIST params if the client doesn't supply any (e.g., >3), to reduce the (often quite large) number of nearly-empty channels. If you want you could make the server send a little message to the client noting that it has added the default. It would help with reducing a lot of unnecessarily load/bandwidth on larger networks. Thoughts? | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
| has duplicate | 0002489 | closed | Suggestion: not displaying channels with less than 2 ppl in /list |
|
|
Sounds interesting, but I think this will create more problems. People already don't understand why mIRC hides non-alphanumeric channels, and the option for that is quite obvious. I can only imagine how many people will be comming to the support channels telling is things like "/list doesn't show my official-channels from the conf when they are empty", or "I have channels with 1 user in them and they aren't showing!", etc. I think this should be something that should be done with a module that overrides the LIST command. |
|
|
that's why it should be optional not mandatory |
|
|
I tend to agree, this seems better suited to a module. First, people are going to want more. You say >3, well someone is going to want >4. So the number must be configurable. Then there will be people who also want it to only show channels with <100, or only channels created >5 minutes ago, etc. It seems easier for a module, especially since the code for this module would only be like 3 lines! |
|
|
Never mind about modules, IMHO this is something that should be handled client-side (X-Chat already does this, for example), not server-side. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-02-08 17:30 | fez | New Issue | |
| 2005-02-09 00:58 | Stealth | Note Added: 0009052 | |
| 2005-02-09 01:34 | fez | Note Added: 0009053 | |
| 2005-02-09 23:33 |
|
Note Added: 0009060 | |
| 2005-02-19 14:07 | Ron2K | Note Added: 0009181 | |
| 2005-02-19 14:25 | syzop | Status | new => closed |
| 2006-11-23 13:34 | syzop | Relationship added | has duplicate 0002489 |
