starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-10 00:08:52 +02:00

[GH-ISSUE #805] Linux client #568

New issue

Closed

opened 2026-05-07 00:25:30 +02:00 by BreizhHardware · 12 comments

BreizhHardware commented

2026-05-07 00:25:30 +02:00

Owner

Originally created by @johnlpe on GitHub (Jul 5, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/805

Please client for Linux.

https://github.com/binwiederhier/ntfy/pull/75

Spec: https://unifiedpush.org/spec/dbus/

Originally created by @johnlpe on GitHub (Jul 5, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/805 Please [client](https://f-droid.org/en/packages/io.heckel.ntfy/) for Linux. https://github.com/binwiederhier/ntfy/pull/75 Spec: https://unifiedpush.org/spec/dbus/

BreizhHardware

2026-05-07 00:25:30 +02:00

closed this issue
added the
unified-push

enhancement
labels

BreizhHardware commented

2026-05-07 00:25:31 +02:00

Author

Owner

@binwiederhier commented on GitHub (Jul 5, 2023):

Welcome to GitHub. I can't believe you joined just to open this issue. 👋

Afaik @vkrause is working on this as part of https://github.com/KDE/kunifiedpush -- though I am not sure how active the development this is, and if I 100% understood this correctly.

@karmanyaahm may know more.

@binwiederhier commented on GitHub (Jul 5, 2023): Welcome to GitHub. I can't believe you joined just to open this issue. :wave: Afaik @vkrause is working on this as part of https://github.com/KDE/kunifiedpush -- though I am not sure how active the development this is, and if I 100% understood this correctly. @karmanyaahm may know more.

BreizhHardware commented

2026-05-07 00:25:31 +02:00

Author

Owner

@johnlpe commented on GitHub (Jul 5, 2023):

Welcome to GitHub. I can't believe you joined just to open this issue. wave

I prefer local and Codeberg :D

Afaik @vkrause is working on this as part of https://github.com/KDE/kunifiedpush -- though I am not sure how active the development this is, and if I 100% understood this correctly.

AFAIK, KUnifiedPush is only library for applications. Online service -> distributor server (ntfy server) -> distributor client (❗ ntfy client ❗) -> application (that use KUnifiedPush)

@johnlpe commented on GitHub (Jul 5, 2023): > Welcome to GitHub. I can't believe you joined just to open this issue. wave I prefer local and [Codeberg](https://codeberg.org) :D > Afaik @vkrause is working on this as part of https://github.com/KDE/kunifiedpush -- though I am not sure how active the development this is, and if I 100% understood this correctly. AFAIK, KUnifiedPush is only library for applications. Online service -> distributor server (ntfy server) -> distributor client (:exclamation: ntfy client :exclamation:) -> application (that use KUnifiedPush)

BreizhHardware commented

2026-05-07 00:25:31 +02:00

Author

Owner

@johnlpe commented on GitHub (Jul 5, 2023):

Stupid question: why unified-push tag? I mean ntfy support only UnifiedPush, right?

@johnlpe commented on GitHub (Jul 5, 2023): Stupid question: why unified-push tag? I mean ntfy support only UnifiedPush, right?

BreizhHardware commented

2026-05-07 00:25:31 +02:00

Author

Owner

@vkrause commented on GitHub (Jul 5, 2023):

Afaik @vkrause is working on this as part of https://github.com/KDE/kunifiedpush -- though I am not sure how active the development this is, and if I 100% understood this correctly.

The code mostly works, the remaining blockers to actually release this are the Flatpak portal push notification API as well as getting the server infrastructure in place for our users not having access to this otherwise (so applications can actually rely on push notifications). The latter involves some non-technical aspects and isn't particularly fast or visible work indeed.

@vkrause commented on GitHub (Jul 5, 2023): > Afaik @vkrause is working on this as part of https://github.com/KDE/kunifiedpush -- though I am not sure how active the development this is, and if I 100% understood this correctly. The code mostly works, the remaining blockers to actually release this are the Flatpak portal push notification API as well as getting the server infrastructure in place for our users not having access to this otherwise (so applications can actually rely on push notifications). The latter involves some non-technical aspects and isn't particularly fast or visible work indeed.

BreizhHardware commented

2026-05-07 00:25:31 +02:00

Author

Owner

@karmanyaahm commented on GitHub (Jul 5, 2023):

Stupid question: why unified-push tag? I mean ntfy support only UnifiedPush, right?

ntfy is a wide-ranging service that supports sending notifications between any two devices. For regular ntfy notifications, there is already a Linux CLI: https://docs.ntfy.sh/subscribe/cli/.

UnifiedPush is just one of many additional features of ntfy, and inherently, a UnifiedPush ntfy distributor would distribute notifications from the ntfy app to various applications. The KUnifiedPush distributor supports ntfy and other servers.

@karmanyaahm commented on GitHub (Jul 5, 2023): > Stupid question: why unified-push tag? I mean ntfy support only UnifiedPush, right? ntfy is a wide-ranging service that supports sending notifications between any two devices. For regular ntfy notifications, there is already a Linux CLI: https://docs.ntfy.sh/subscribe/cli/. UnifiedPush is just one of many additional features of ntfy, and inherently, a UnifiedPush ntfy distributor would *distribute* notifications from the ntfy app to various applications. The KUnifiedPush distributor supports ntfy and other servers.

BreizhHardware commented

2026-05-07 00:25:31 +02:00

Author

Owner

@osering commented on GitHub (Jan 3, 2024):

Linux client would be beneficial, as more and more arm64/aarch64 devices run linux - raspberryPi (and other berries&boards), tvboxes, armbian, ubuntu touch, jolla, WebOs, Tizen, Enigma e.t.c.
The optimal concept would be Command Line client (demon) and (optional) GUI - like Android client frontend. Together with Mqtt could be integrated in home automation systems.
P.S. FreeBSD/TrueOS (mainly servers) client could be considered as well.
P.P.S. Unfortunately KDE usually has many dependences, so more resource hungry and not optimal on headless systems.

@osering commented on GitHub (Jan 3, 2024): Linux client would be beneficial, as more and more arm64/aarch64 devices run linux - raspberryPi (and other berries&boards), tvboxes, armbian, ubuntu touch, jolla, WebOs, Tizen, Enigma e.t.c. The optimal concept would be Command Line client (demon) and (optional) GUI - like Android client frontend. Together with Mqtt could be integrated in home automation systems. P.S. FreeBSD/TrueOS (mainly servers) client could be considered as well. P.P.S. Unfortunately KDE usually has many dependences, so more resource hungry and not optimal on headless systems.

BreizhHardware commented

2026-05-07 00:25:32 +02:00

Author

Owner

@mmBesar commented on GitHub (Dec 7, 2024):

Very much needed!

@mmBesar commented on GitHub (Dec 7, 2024): Very much needed!

BreizhHardware commented

2026-05-07 00:25:32 +02:00

Author

Owner

@wunter8 commented on GitHub (Dec 7, 2024):

@mmBesar what are you trying to achieve? Are you just looking for a desktop GUI program? What about installing the web app as a standalone app as a PWA?

If you just want pop-up desktop notifications (and don't necessarily need a desktop GUI for sending messages), another option would be to use the ntfy CLI client daemon to listen for incoming messages and call something like notify-send to create a pop-up notification for each message that comes in

@wunter8 commented on GitHub (Dec 7, 2024): @mmBesar what are you trying to achieve? Are you just looking for a desktop GUI program? What about installing the web app as a standalone app as a PWA? If you just want pop-up desktop notifications (and don't necessarily need a desktop GUI for sending messages), another option would be to use the ntfy CLI client daemon to listen for incoming messages and call something like `notify-send` to create a pop-up notification for each message that comes in

BreizhHardware commented

2026-05-07 00:25:32 +02:00

Author

Owner

@mmBesar commented on GitHub (Dec 8, 2024):

I did opt for a systemd service running the CLI client, utilizing notify-send.
But, I full native GUI client would be nice, this client not working for me under NixOS / Hyprland!

@mmBesar commented on GitHub (Dec 8, 2024): I did opt for a systemd service running the CLI client, utilizing notify-send. But, I full native GUI client would be nice, [this client](https://github.com/ranfdev/Notify) not working for me under NixOS / Hyprland!

BreizhHardware commented

2026-05-07 00:25:32 +02:00

Author

Owner

@wunter8 commented on GitHub (Dec 8, 2024):

Have you tried any of these? https://docs.ntfy.sh/integrations/#clis-guis

@wunter8 commented on GitHub (Dec 8, 2024): Have you tried any of these? https://docs.ntfy.sh/integrations/#clis-guis

BreizhHardware commented

2026-05-07 00:25:32 +02:00

Author

Owner

@mmBesar commented on GitHub (Dec 8, 2024):

Yes, but I think my simple setup will do for now.
Thank you.

@mmBesar commented on GitHub (Dec 8, 2024): Yes, but I think my simple setup will do for now. Thank you.

BreizhHardware commented

2026-05-07 00:25:32 +02:00

Author

Owner

@k8ieone commented on GitHub (May 20, 2025):