Service
Standard browser Web Push API delivery via VAPID (RFC 8291/8292) — sending a push message directly to a subscribed browser endpoint (Chrome/Firefox/Safari push services) without going through a third-party relay like Pinglet/ntfy/Pushover.
Why now
Web Push is the underlying mechanism several of the "newest favorite" self-hosted tools (ntfy's web client, Pinglet, Pingram) build on top of. Supporting it directly would let self-hosters who run their own PWA/dashboard push straight to a browser subscription without depending on any third-party relay — a genuinely different capability from the other providers in this module (they're all relays; this is direct delivery).
Apprise comparison
Apprise does not have a dedicated Web Push / VAPID plugin — it only supports generic Form/JSON/XML webhook POSTs, which isn't the same as native browser push (requires VAPID key signing and the Push-flavored payload encryption). This would be new ground for both projects.
Proposed scope
This is more involved than the relay-style providers (needs VAPID key pair management, payload encryption per RFC 8291, and a PushSubscription shape as Config/per-recipient input) — likely warrants its own design pass rather than a straight port of the providers/ntfy shape. Flag for discussion before scoping.
Note
Per CLAUDE.md, this repo's near-term policy is to keep the provider list to what's ported from Charon and not add new integrations without an explicit go-ahead. This issue is tracking/backlog only — do not implement without maintainer sign-off.
Service
Standard browser Web Push API delivery via VAPID (RFC 8291/8292) — sending a push message directly to a subscribed browser endpoint (Chrome/Firefox/Safari push services) without going through a third-party relay like Pinglet/ntfy/Pushover.
Why now
Web Push is the underlying mechanism several of the "newest favorite" self-hosted tools (ntfy's web client, Pinglet, Pingram) build on top of. Supporting it directly would let self-hosters who run their own PWA/dashboard push straight to a browser subscription without depending on any third-party relay — a genuinely different capability from the other providers in this module (they're all relays; this is direct delivery).
Apprise comparison
Apprise does not have a dedicated Web Push / VAPID plugin — it only supports generic Form/JSON/XML webhook POSTs, which isn't the same as native browser push (requires VAPID key signing and the
Push-flavored payload encryption). This would be new ground for both projects.Proposed scope
This is more involved than the relay-style providers (needs VAPID key pair management, payload encryption per RFC 8291, and a
PushSubscriptionshape asConfig/per-recipient input) — likely warrants its own design pass rather than a straight port of theproviders/ntfyshape. Flag for discussion before scoping.Note
Per
CLAUDE.md, this repo's near-term policy is to keep the provider list to what's ported from Charon and not add new integrations without an explicit go-ahead. This issue is tracking/backlog only — do not implement without maintainer sign-off.