View Issue Details

IDProjectCategoryView StatusLast Update
0002055unrealircdpublic2007-04-27 05:41
ReporterMekonikum Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionwont fix 
Product Version3.2.1 
Summary0002055: Feature Request: Disable ~& prefixes in listen block (OR umode)
Description~& should be on as default, with an option to switch them of in the listen block (OR with a umode), so users with irc clients which can't use them can connect to an other port to disable them.
3rd party modules

Activities

codemastr

2004-09-04 15:24

reporter   ~0007509

That's really not possible.

Could you tell me which clients out there still don't support this?

Mekonikum

2004-09-04 21:30

reporter   ~0007526

Klient for example (the free Version), or many Script's based on mIRC which colors the prefixes.
Yes, I know, those reasons are crap, but the users ... the users ...
We made a voting, 80% would like the ~&, 20% hate them, it would be great if that users could make this decision by oneself.

codemastr

2004-09-04 22:51

reporter   ~0007527

Well the thing is, the system is more than just "Display an &." There is more to it than that. It's not something we can just turn on/off easily. And even if we could, it would slow things down because extra checks would need to be done to determine whether it is on.

But as for the specific things you mentioned, Klient 1.x (the free one) will have many other compatibility issues, not just prefixes. That's a very old version of Klient. Users are of course free to use old versions, but when things don't work, you know why. It would be like complaining to Microsoft that software doesn't work on Windows 3.1, it's old and not compatible with current practices. Klient 2.0.16 does fully support prefixes though.

And as for mIRC scripts, well that's easy enough to fix. mIRC supports the means for scripts to color any prefix. It would just require someone to modify the script.

aquanight

2004-09-05 05:01

reporter   ~0007537

I think some of the more "traditional" clients still do not yet support 005 PREFIX=. For example, the current stable release of irssi does not (their development release does as the [Unreal's] FAQ mentions, but not the official release AFAIK). I can't think of any others at the moment...

The need for selecting a port isn't necessary though. If client-server capability negotiation ever becomes standard, clients would simply tell the server "we only support these prefixes" and the server basically says "I have these prefixes out of the ones you support." Or something to that effect.

codemastr

2004-09-05 16:35

reporter   ~0007541

Well I agree negotiation would solve this. However, if some clients are so hesitant to add 005 support, imagine how long it will be before they add capability negotiation!

Anyway, irssi is the only "common" client I know of that really doesn't support it at all. Even epic supports it!

al5001

2004-09-05 19:26

reporter   ~0007542

I really don't know what you guys are going on about. I've used the mIRC Windows IRC Client for ages, and even edited UnrealIRCd to have * for channel owner, ^ for channel admin, # for channel operator, and the two others unchanged used for 1 server on a test network. The mIRC IRC client even shows the # sign beside my name in every newly created channel! What a coincidence! I have yet to figure out what you mean by "clients don't support blah blah blah", because from my experience, I have not had any problems.

codemastr

2004-09-05 20:04

reporter   ~0007544

al5001, indeed, but mIRC != irssi.

al5001

2004-09-07 01:08

reporter   ~0007569

irssi? Heh, why don't people use something better like ircII or epic?...or hell, let's get graphical here-- XChat or mIRC? If irssi doesn't want to take the time to fix their own client to accept any prefix, that's their problem. There are many more clients that will accept any prefix.

aquanight

2004-09-07 01:36

reporter   ~0007570

al5001, did you not read my post? The development build of irssi does support the prefixes.

stskeeps

2007-04-27 05:41

reporter   ~0013831

Please re-submit for 3.3 or 3.2.6/7 instead if this issue still exists.

Issue History

Date Modified Username Field Change
2004-09-04 09:59 Mekonikum New Issue
2004-09-04 15:24 codemastr Note Added: 0007509
2004-09-04 21:30 Mekonikum Note Added: 0007526
2004-09-04 22:51 codemastr Note Added: 0007527
2004-09-05 05:01 aquanight Note Added: 0007537
2004-09-05 16:35 codemastr Note Added: 0007541
2004-09-05 19:26 al5001 Note Added: 0007542
2004-09-05 20:04 codemastr Note Added: 0007544
2004-09-07 01:08 al5001 Note Added: 0007569
2004-09-07 01:36 aquanight Note Added: 0007570
2007-04-27 05:41 stskeeps Status new => closed
2007-04-27 05:41 stskeeps Note Added: 0013831
2007-04-27 05:41 stskeeps Resolution open => wont fix