Bug 485111

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
The body of new message notifications contain a list of every message posted while NeoChat was in the background since the application was open. This causes the notification to become unreadable within two or three messages on macOS.

STEPS TO REPRODUCE
1. Receive a message while NeoChat is running in the background. A macOS notification should appear.
2. Wait for multiple messages to be sent while NeoChat is in the background.

OBSERVED RESULT

Multiple notifications are received with redundant information. For example, if @alice:example.com sends messages in a given room, the following notifications may appear (from oldest to newest):

"""
alice (@alice:example.com): message one
"""

"""
alice (@alice:example.com): message one
alice (@alice:example.com): message two
"""


"""
alice (@alice:example.com): message one
alice (@alice:example.com): message two ...
"""

Any further messages will look identical.

EXPECTED RESULT

Given the same messages, notifications should look more like:

"""
alice (@alice:example.com): message one
"""

"""
alice (@alice:example.com): message two
"""

"""
alice (@alice:example.com): message three
"""

... and so on.

SOFTWARE/OS VERSIONS
macOS Sonoma 14.4 (using KDE Craft)
KDE Plasma Version: N/A
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

Possibly a duplicate of #475228 (https://bugs.kde.org/show_bug.cgi?id=475228), although since it makes notifications unusable in macOS, it seems more like a bug than feature request.

To work around this, I modified `NotificationsManager::postNotification` in my source tree to not store a KNotification for each room.