[Feature] Keep history of "consumed" notifications

[pwnfooj716]

Just went through a round of trying out all the different wayland capable notification daemons and was blown away when I found this one. It just works exactly how I want it to and looks beautiful too!

The only thing I miss from other daemons out there such as dunst is the ability to view the past history of notifications that have been either dismissed or "acted upon" by an action. I liked how I could just pop notifications from the history at the press of a key (even if they are just "read-only"). Currently with swaync, once a notification has been consumed it's gone forever.

Personally, I wouldn't even change much about the interface of the panel at all. Maybe a widget could be added to open up the notification history and you could just scroll through it and then click a button and it goes away again. Something simple like that would suffice. The number of items to keep in the history should also be configurable in the config file.

Lastly, it would just be nice if there was a saync-client command to pop notifications from the history and have them show up on the screen until you click them away. That way this can be set to a keybind for quick access to recent notifications.

[ErikReider]

Adding that as a command sounds like a good idea and would be pretty "simple" to add. I don't really have that much time right now so could take a while

are there any News on this issue?

[mesmerx]

+1 it will be very usefull

[ArijanJ]

I forked this and added basic sqlite notification storage with no UI, it simply prints the entire full database with swaync-client -sh

Note that the database is unencrypted and and the API is likely broken as the entire thing was made with an LLM. Ideally it would be encrypted like how CopyQ does it and we would have UI that works

Right now I just do "on-click-middle": "zenity --entry --text \"$(swaync-client -sh)\"", in my waybar configuration to read the history

https://github.com/ArijanJ/SwayNotificationCenter (under history branch)

[ArijanJ]

I'll try doing this sometime this week, but I think I'll only do it in-memory for the running session (should be pretty easy, on delete store the notification, on swaync-client --restore add_notification() and pop from the stack).

On restart the history would be gone. Later maybe we could add on-disk storage and encryption.

I would personally want memory only notifications history.
even if there is an on disc + encrypted version I would want to disable that

that's the primary reason I didn't try out your fork

[ArijanJ]

Need to figure out a few things regarding the behavior, but #578 is a start, if anyone has opinions you can share them there

[ErikReider]

Need to figure out a few things regarding the behavior, but #578 is a start, if anyone has opinions you can share them there

Sorry for the extremely late response, the PR got lost in my email notifications. I think that a good start would be to implement the SQLite DB before the restore previous functionality. One thing to consider here is how the DB should be encrypted. Probably the whole file and not each field (sounds like cache miss hell to me xD)