Collect/Group/Debounce Notifications

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
I don't get notifications often but when I do I get so many at once, that they are unusable. A typical scenario is the "XXX file was downloaded via a public link" notification. Instead of getting it once, I might get it 20 times for the same file and then I'll get one for each file downloaded too.

Describe the solution you'd like
I think the server should group notifications for related actions that happen in quick succession. This requires a delay before sending notifications which may be configurable in the future. But even a short, hard-coded delay (like 30 seconds) would vastly improve the user experience.

So instead of getting a notification for each download of a single file, I want to get one notification that says "File XXX was downloaded n times". And instead of getting one notification per file, I'd like one the says "File XXX and n others were downloaded". Ideally, with a way to find out which files those "n others" are (e.g. via a hyperlink) but this is also not a hard requirement for a first draft.

Describe alternatives you've considered
Better notification management. Being able to filter and multi-select notifications will make dealing with overwhelming amounts of notifications easier too. This is also a good feature to have but beyond the scope of this issue.

No files, tests, or entry points are identified in the issue. Start by locating the server's notification handling and the download notification flow, then determine how related events could be delayed and grouped. Done should include grouped messages for repeated or multiple file downloads without losing access to the relevant files.