Support for ntfy as unifiedpush gateway

[williamkray]

Describe the problem

Currently Cinny handles push notifications natively from the homeserver pushers. However, mobile browsers on Android trend to have issues reliably sending notifications, so users may still have apps like element installed for push notifications, only to use cinny in their browser to access their messages.

Describe the solution you'd like

I would like Cinny to allow configuration to register as a notification endpoint with ntfy.sh servers, so that notifications could be pushed reliable to Android devices via the ntfy app, and sent to the PWA on the users device, eliminating the need to keep a second matrix client installed.

Alternatives considered

Resolving notification reliability natively via an app bundle: would still benefit from using ntfy as a secondary option.

Additional context

No response

[C0ffeeCode]

Do you just want the message pushed via ntfy or do you want it to integrate?
Opening Cinny with a specific channel is not possible with Cinny at the moment,
but this can be addressed using URL fragments (#411), which I'd say displays the best approach.

[williamkray]

i mean integration with deep links would be great, but i'd take baby steps with a plan for iterative improvement over nothing.

[C0ffeeCode]

I do not think these fits into Cinny properly imo, but you could do that manually.

[Handrail9]

I would like to mention in addition to OPs issue, it would be beneficial to support all UP (UnifiedPush) implementations and not just ntfy.sh. I use NextPush but Ntfy, NextPush, FCM-UP etc. all use the same UnifiedPush API.

[Atemu]

I think it'd be better to implement support for WebPush instead and leave it up to the user agent to implement the web push via its preferred back-end – whether that's UP, FCM, APN, XMPP or Autopush.