[GH-ISSUE #1036] Use different distributor for ntfy (Android) #727

New issue

Closed

opened 2026-05-07 00:26:57 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:26:57 +02:00

Owner

Originally created by @mrusme on GitHub (Feb 26, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1036

💡 Idea
I'm running Conversations (app), which is already a distributor for UnifiedPush and hence keeping a connection open. I would like to use ntfy to send custom push notifications from the CLI, and I would like ntfy (Android) to use Conversations as a distributor app, to not have two apps keeping connections open in the background.

💻 Target components
ntfy Android, server

Originally created by @mrusme on GitHub (Feb 26, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1036 :bulb: **Idea** I'm running Conversations (app), which is already a distributor for UnifiedPush and hence keeping a connection open. I would like to use ntfy to send custom push notifications from the CLI, and I would like ntfy (Android) to use Conversations as a distributor app, to not have two apps keeping connections open in the background. :computer: **Target components** ntfy Android, server

BreizhHardware

2026-05-07 00:26:57 +02:00

closed this issue
added the
enhancement

unified-push
labels

BreizhHardware commented

2026-05-07 00:26:58 +02:00

Author

Owner

@binwiederhier commented on GitHub (Jan 5, 2026):

I'm not sure I understand. ntfy is a UnifiedPush distributor, it doesn't use a distributor

@binwiederhier commented on GitHub (Jan 5, 2026): I'm not sure I understand. ntfy is a UnifiedPush distributor, it doesn't use a distributor

BreizhHardware commented

2026-05-07 00:26:58 +02:00

Author

Owner

@mrusme commented on GitHub (Jan 15, 2026):

That was understood. The request was to implement a mode in which ntfy can be used alongside an existing distributor, by acting solely as an UP client that allows triggering notifications on the phone via CLI tool.

However, after now almost two years this issue is no longer relevant to me. For anyone who had upvoted the issue: I solved what I intended to do using simple XMPP messages/notifications via Overpush/msg.taxi.

I have no more need for ntfy and can close this issue.

@mrusme commented on GitHub (Jan 15, 2026): That was understood. The request was to implement a mode in which ntfy can be used alongside an existing distributor, by acting solely as an UP client that allows triggering notifications on the phone via CLI tool. However, after now almost two years this issue is no longer relevant to me. For anyone who had upvoted the issue: I solved what I intended to do using simple XMPP messages/notifications via [Overpush](https://codeberg.org/mrus/overpush)/[msg.taxi](https://msg.taxi). I have no more need for ntfy and can close this issue.

BreizhHardware referenced this issue

2026-05-07 01:01:54 +02:00

[PR #727] [MERGED] WIP: Access API #1394