View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006116 | unreal | ircd | public | 2022-05-27 00:32 | 2022-05-27 08:57 |
| Reporter | ZarTek-Creole | Assigned To | syzop | ||
| Priority | low | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | 6.0.3 | ||||
| Summary | 0006116: HISTORY PREFIX PLAYBACK | ||||
| Description | the playback is completely transparent. This can be annoying when using a robot. commands run again when joining a channel +H For example if you have a public command to restart your eggdrop, it will restart indefinitely I know this has nothing to do with unrealircd and its HISTORY mode. 1) I want to offer the possibility to prefix the playback set { history { prefix "replay:" // prefix "*" } } [26-05/23:46] <pyro> lol [26-05/23:53] * Attempting to rejoin channel #Extra-Cool [26-05/23:46] <pyro> replay: lol or [26-05/23:46] <pyro> lol [26-05/23:53] * Attempting to rejoin channel #Extra-Cool [26-05/23:46] <replay> pyro: lol Another possibility is to have a umode (+h is free) to have playbacks or not. some people prefer to deactivate and use the playback of their znc or the logs of their irc client here are some suggestions. Is there a way to prevent my eggdrop from listening to playback and only listening to new messages? with the CAPs(message)? | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Hello, yes. If you enable `draft/chathistory` cap when connecting, you are indicating to the server that you are going to ask for any chat history that you need. Then, when you join a channel with +H, and as expected your eggdrop does NOT ask for any history, it will not receive any, and it will not trigger the commands. I'm not sure where in the eggdrop configuration you can specify the caps, but all you need to do is add `draft/chathistory` into your eggdrop CAP requests, and it will solve the problem of the playback command triggers. Have a great day! |
|
|
Thank you, i have set i my eggdrop that: set cap-request "draft/chathistory" work perfectly! Beautiful day! |
|
|
Thanks for reporting back the solution for you, can be useful for others. Still, I stand by what I already said in 0005818 about this (which is a duplicate of this), that it should be fixed upstream by the bot maker / developer: Such as this comment https://bugs.unrealircd.org/view.php?id=5818#c21975: "This affects bots that implement "server-time" but can't cope with the history on join somehow. Or am I missing something? Surely it should be really easy for such a bot to fix it, to simply ignore everything inside the chathistory batch? I mean: we are talking about bots that implement "server-time" but are either missing support for "batch" or for specific logic to ignore the chathistory batch." and the final comment in there too: "I'm closing this one. This problem limits itself to software that supports "server-time" but does not ignore "chat-history" batches. I suggest anyone experiencing that problem to take it up with the bot software developer(s). If those devs feel this is a problem too, then they should not fire scripts on history or fire events in a different way, whatever they like.. up to them. If the bot developer does not see this as a problem, then why should we?" |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-05-27 00:32 | ZarTek-Creole | New Issue | |
| 2022-05-27 00:36 | Valware | Note Added: 0022524 | |
| 2022-05-27 01:35 | ZarTek-Creole | Note Added: 0022527 | |
| 2022-05-27 08:51 | syzop | Relationship added | duplicate of 0005818 |
| 2022-05-27 08:53 | syzop | Assigned To | => syzop |
| 2022-05-27 08:53 | syzop | Status | new => closed |
| 2022-05-27 08:53 | syzop | Resolution | open => duplicate |
| 2022-05-27 08:53 | syzop | Note Added: 0022530 | |
| 2022-05-27 08:55 | syzop | Note Edited: 0022530 | |
| 2022-05-27 08:57 | syzop | Note Edited: 0022530 |
