My god, it's full of segfaults

commhistory-daemon (patched)

As explained in the gabble page, a carbon enabled client will receive copies of the messages sent by another of your resources. If that resource supports and sends read markers, your carbon receiving client would be able to remove the related notifications.

The commhistory-daemon is also responsible for handling notifications and can easily modified to remove them due to read notifications.



Impressum / Legal / Privacy