View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006109 | unreal | ircd | public | 2022-05-22 22:41 | 2022-05-25 09:46 |
| Reporter | PeGaSuS | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Platform | Linux | OS | Ubuntu | OS Version | 20.04 |
| Summary | 0006109: Implement WHISPER command | ||||
| Description | This talk appears once in a while on IRC, about implementing this: https://www.mdbnet.net/ircx/ch03s13.html Some say that this could be useful. Throwing it here so devs can give it some thought and the idea won't get lost in time. Cheers! | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I have a whisper module for UnrealIRCd 3.2.x dated 2005 (without fallback to non-ircx). I am not sure the documentation at https://www.mdbnet.net/ircx/ch03s13.html is accurate though. The problem part is the fallback for non-ircx and I remember clearly that on IRCX servers around the year 2000 that "WHISPER #channel User :he sucks" would either end up in channel as a "PRIVMSG #channel :he sucks" or at least displayed exactly like that by mIRC. This would cause quite some abuse and "fun" because then it would look like people would be sending messages in a channel that other people could not see, and you could not see the difference. Combine that with 2 or 3 people doing that you had a whole fake side-conversation, including insults and fights, and channel ops did not seem to react (because they never saw the message)... like I said, it was much fun ;D. The spec on mdbnet seems to suggest it was the other way around, and that the fallback option was to deliver as private message. The problem with that is that things that were meant to be in-channel suddenly popped up a query window, but that is less abusive. Anyway, that was more about the history of the thing and the side-effects... As for "do we want this?"... I don't know. Clearly I never thought it should have been in otherwise I would not have made it a 3rd party module 17 years ago. And now we have "channel-context"? I would think that, since most other IRCds had no interest in implementing WHISPER in the past, and channel-context being a simple extension of a way we are already engaging (message tags), it is the way to go and not WHISPER? |
|
|
FWIW: I think the /WHISPER command, if implemented at all, should be a client command (not a server command) which harnesses `channel-context`. Quick and dirty mIRC script for /WHISPER which uses `channel-context` attached [09:41:49] [Whisper from testing2] hi there! [09:41:59] [Whisper to testing2] oh hi! The reason I think it should be a client command is because it's much easier to determine the active channel when sending whispers like /whisper <nick> <message> otherwise, I'd be right on this :P |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-05-22 22:41 | PeGaSuS | New Issue | |
| 2022-05-23 08:16 | syzop | Note Added: 0022497 | |
| 2022-05-23 10:44 | Valware | Note Added: 0022508 | |
| 2022-05-23 10:44 | Valware | File Added: whisper.txt | |
| 2022-05-25 09:46 | syzop | Assigned To | => syzop |
| 2022-05-25 09:46 | syzop | Status | new => closed |
| 2022-05-25 09:46 | syzop | Resolution | open => no change required |
