Push dispatch on offline delivery (content-free)

[codebestia]

In the delivery pipeline, when a recipient device has NO active socket, send a Web Push to that device's subscriptions. The payload contains NO message content — only { type, conversationId, messageId }. On open, client syncs and decrypts locally. Never put ciphertext or sender content in the push.

Acceptance criteria:

• Push fires only when the device is offline
• Payload carries no content/ciphertext
• On open, client syncs + decrypts

[DevALVIN-24]

@DevALVIN-24 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 @DevALVIN-24 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 team,

I have worked on real-time messaging systems that combine persistent connections with push notification fallbacks to ensure users receive timely updates regardless of their connection state. My focus has been on building reliable delivery pipelines while preserving user privacy and minimizing unnecessary network traffic.

For this issue, I'll extend the delivery pipeline to detect when recipient devices are offline and trigger a content-free Web Push containing only the required metadata. I'll ensure encrypted message content is never included in the notification payload, and that clients synchronize and decrypt messages locally after opening the notification, keeping the implementation aligned with the project's security model.

ℹ️ 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 🌊