Service
Bark — a popular iOS push notification app with an open-source, self-hostable server (bark-server). Notifications are sent as a simple HTTP GET/POST to the Bark server, which relays to the device via APNs.
Why now
A long-standing homelab/self-hosting favorite specifically for iOS users who find ntfy's iOS app less native-feeling — regularly recommended alongside ntfy/Gotify in self-hosting communities.
Apprise comparison
Apprise supports Bark (bark://) — a gap versus Apprise's coverage today.
Proposed scope
Mirror providers/gotify shape (simple URL + Token POST):
providers/bark packageConfig{ ServerURL, DeviceKey }New(cfg, wrapper) *Client, (*Client).Send(ctx, notify.Message) error via transport.Wrapper
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
Bark — a popular iOS push notification app with an open-source, self-hostable server (bark-server). Notifications are sent as a simple HTTP GET/POST to the Bark server, which relays to the device via APNs.
Why now
A long-standing homelab/self-hosting favorite specifically for iOS users who find ntfy's iOS app less native-feeling — regularly recommended alongside ntfy/Gotify in self-hosting communities.
Apprise comparison
Apprise supports Bark (
bark://) — a gap versus Apprise's coverage today.Proposed scope
Mirror
providers/gotifyshape (simpleURL+TokenPOST):providers/barkpackageConfig{ ServerURL, DeviceKey }New(cfg, wrapper) *Client,(*Client).Send(ctx, notify.Message) errorviatransport.WrapperNote
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.