View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004312 | unreal | ircd | public | 2014-06-02 12:51 | 2014-06-02 19:13 |
| Reporter | Amiga600 | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2.10 | ||||
| Summary | 0004312: Sorting in Ban / Invite / Exception Lists | ||||
| Description | Please consider my request to have extended bans placed alphabetically (by date of course) below normal bans in the banlist, in a similar way to other ircds (namely hyperion places mutebans (%nick!*@*) below other normal standard bans) Example: nick1!*@* ~n:nick1!*@* ~q:nick2!*@* etc. | ||||
| Steps To Reproduce | as above | ||||
| 3rd party modules | |||||
|
|
Bans are sent in the order they are set. Any additional sorting (alphabetically, user, etc) is something that should be done by the client. The IRC server is just to send information to a client that displays the information as desired, in fancy windows, with fancy formatting. |
|
|
I should point out that, for example in mIRC, if you double click on a channel to get Channel Central with the banlist: * this list isn't sorted * if you double clicked and saw this screen, then close it, someone adds a ban, then double click again, the server isn't even queried for the ban list. This is because mIRC already knows only one ban was added, otherwise it would have seen an unban / other ban. So we can't even force sorting here, it doesn't matter what the server does as it isn't even queried. So for, for example, mIRC it would be useless to sort the channel list server-side. Other clients may behave the same (if they are efficient :P). I also tend to agree with Stealth that sorting can perfectly be done on the client side. Just like is done with /LIST. I just wanted to post a little longer / in-depth comment ;P |
