adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-11-03 02:42:21 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

Inconsistent handling of STATUSMSG messages in logs. #679

New Issue
Open
opened 2026-10-05 04:38:00 +02:00 by adam · 3 comments
adam commented 2026-10-05 04:38:00 +02:00
Owner
Copy link
Copy source

In incoming messages to @#channel, $WINDOW gets substituted to #channel, whereas in outgoing messages to @#channel $WINDOW gets substituted to @#channel. Because of this, incoming statusmsg messages are included in the channel logs, while outgoing statusmsgs are not.

Given that it's currently impossible to distinguish statusmsg messages from regular ones I think the better solution is to make all statusmsgs log to <status>#channel, as opposed to including them both in the channel log.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30375928-inconsistent-handling-of-statusmsg-messages-in-logs?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
In incoming messages to `@#channel`, $WINDOW gets substituted to `#channel`, whereas in outgoing messages to `@#channel` $WINDOW gets substituted to `@#channel`. Because of this, incoming statusmsg messages are included in the channel logs, while outgoing statusmsgs are not. Given that it's currently impossible to distinguish statusmsg messages from regular ones I think the better solution is to make all statusmsgs log to `<status>#channel`, as opposed to including them both in the channel log. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30375928-inconsistent-handling-of-statusmsg-messages-in-logs?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin> <!-- github-sync-id:130078399 -->
adam commented 2026-10-05 04:38:01 +02:00
Author
Owner
Copy link
Copy source

I think this is fixed in git.

I think this is fixed in git. <!-- github-comment-id:177423562 -->
adam commented 2026-10-05 04:38:02 +02:00
Author
Owner
Copy link
Copy source

I could reproduce it on 10785ee

I could reproduce it on 10785ee <!-- github-comment-id:177602113 -->
adam commented 2026-10-05 04:38:03 +02:00
Author
Owner
Copy link
Copy source

A possibly related issue is that incoming statusmsg messages are included in the channel buffer while outgoing are not.

A possibly related issue is that incoming statusmsg messages are included in the channel buffer while outgoing are not. <!-- github-comment-id:177620150 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#679