Notification coalescing / rate limiting

[codebestia]

Coalesce bursts (e.g. many messages in one conversation) into a single "N new messages" push and rate-limit per device to avoid spam. Still content-free.

Acceptance criteria:

• Bursts coalesced into one push
• Per-device push rate-limited
• Counts accurate ("3 new messages")

[TheShnider]

@TheShnider has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi. I have reviewed this issue and would like to work on it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheShnider to this issue.

[modecodes]

@modecodes has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue! because I am very conversant with solving problems like this, and i can submit the pr with 48hr

ℹ️ Repo Maintainers: To accept this application, review their application or assign @modecodes to this issue.

[Depo-dev]

@Depo-dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day team, my name is Depodev, I have gone through the issue requirements and i am confident i can deliver and i will like to work on this.

ETA: 24 hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Depo-dev to this issue.

[Chidimj]

@Chidimj has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Clicked maintainers,

I've contributed to notification systems where reducing notification fatigue is just as important as ensuring timely delivery. My experience includes implementing batching strategies, rate-limiting mechanisms, and accurate event aggregation to improve user experience while preventing excessive notification traffic.

For this issue, I'll implement notification coalescing that combines message bursts into a single push while maintaining accurate unread counts. I'll also introduce per-device rate limiting to prevent notification spam without delaying important updates, ensuring the notification payload remains content-free and consistent with the project's privacy requirements.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chidimj to this issue.

[drips-wave]

Congratulations, @Chidimj! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Chidimj: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊