Bug 398046 - Flood of notifications upon reconnecting
Summary: Flood of notifications upon reconnecting
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: notifications (show other bugs)
Version: 1.7.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-30 03:03 UTC by Nate Graham
Modified: 2022-12-30 05:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2018-08-30 03:03:34 UTC
I use a bouncer and have Plasma notifications turned on for every single message in every channel. The notification-per-message works great for me when Konversation is already running, but when I turn on Konversation in the morning, the result is a flood of notifications from everything the bouncer cached while I was sleeping. Obviously this is not very useful. :)

It would be nice if Konversation could suppress notifications for a bit as soon as it starts up, or suppress notifications originating from bouncer-provided messages that exceed a certain rate, or something like that (feel free to discard those ideas as they are borns from zero familiarity with either Konversation's codebase or even how IRC actually works and what it supports).
Comment 1 Justin Zobel 2022-11-30 05:28:25 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Nate Graham 2022-11-30 14:43:41 UTC
Probably still happening, but I don't use Konversation or IRC anymore to be able to check it.
Comment 3 Bug Janitor Service 2022-12-15 05:13:50 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-30 05:24:29 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!