starred/ntfy

Fork 0

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

[GH-ISSUE #808] Authencation support #572

New issue

Closed

opened 2026-05-07 00:25:32 +02:00 by BreizhHardware · 8 comments

BreizhHardware commented

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

Owner

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

Add support for authencation between application service -- ntfy instance and ntfy instace -- ntfy client.

Originally created by @johnlpe on GitHub (Jul 5, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/808 Add support for authencation between application service -- ntfy instance and ntfy instace -- ntfy client.

BreizhHardware

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

closed this issue
added the
enhancement
label

BreizhHardware commented

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

Author

Owner

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

The GitHub issues have a template format for a reason. Please use it next time.

With these one sentence tickets, it's very hard to understand what you are even talking about. Please be more verbose.

ntfy has a sophisticated auth framework, see: https://docs.ntfy.sh/config/#access-control

@binwiederhier commented on GitHub (Jul 5, 2023): The GitHub issues have a template format for a reason. Please use it next time. With these one sentence tickets, it's very hard to understand what you are even talking about. Please be more verbose. ntfy has a sophisticated auth framework, see: https://docs.ntfy.sh/config/#access-control

BreizhHardware commented

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

Author

Owner

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

Now notification aren't password protected and you have to order topics. I want something like this:

I want to use mastodon.social and push notifications via ntfy.sh. I have installed Tusky and ntfy-client.

I register ntfy.sh with username: example, passwowd: passoword1 and set follows for the application services (one for all or own for each) username: example, password: password2.
I register mastodon.social and add my notification server details. They are: URL: ntfy.sh, username: example, password: password2.

Then when mastodon.social want send push notification to my device:

mastodon.social send notification according to details I gave it: ntfy.sh, example, password2.
ntfy.sh send notification to my phone with connection that is opened by ntfy client.
ntfy client send notification to my notification bus (e.g. Dbus).

@johnlpe commented on GitHub (Jul 5, 2023): Now notification aren't password protected and you have to order topics. I want something like this: I want to use mastodon.social and push notifications via ntfy.sh. I have installed Tusky and ntfy-client. 1. I register ntfy.sh with `username: example`,` passwowd: passoword1` and set follows for the application services (one for all or own for each) `username: example`, `password: password2`. 3. I register mastodon.social and add my notification server details. They are: `URL: ntfy.sh`, `username: example`, `password: password2`. Then when mastodon.social want send push notification to my device: 1. mastodon.social send notification according to details I gave it: `ntfy.sh, example, password2`. 2. ntfy.sh send notification to my phone with connection that is opened by ntfy client. 5. ntfy client send notification to my notification bus (e.g. Dbus).

BreizhHardware commented

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

Author

Owner

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

It sounds like you're describing what UnifiedPush already does. And Tusky specifically already supports UnifiedPush with ntfy (https://github.com/tuskyapp/faq/blob/main/README.md#notifications)

@wunter8 commented on GitHub (Jul 5, 2023): It sounds like you're describing what UnifiedPush already does. And Tusky specifically already supports UnifiedPush with ntfy (https://github.com/tuskyapp/faq/blob/main/README.md#notifications)

BreizhHardware commented

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

Author

Owner

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

It sounds like you're describing what UnifiedPush already does. And Tusky specifically already supports UnifiedPush with ntfy (https://github.com/tuskyapp/faq/blob/main/README.md#notifications)

Of course, ntfy is specifically UnifiedPush notification software (right?), but the problem is lack of authentication.

@johnlpe commented on GitHub (Jul 5, 2023): > It sounds like you're describing what UnifiedPush already does. And Tusky specifically already supports UnifiedPush with ntfy (https://github.com/tuskyapp/faq/blob/main/README.md#notifications) Of course, ntfy is specifically UnifiedPush notification software (right?), but the problem is lack of authentication.

BreizhHardware commented

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

Author

Owner

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

ntfy supports UnifiedPush, but it can be (and often is) used without it.

When using UnifiedPush, a randomly generated ntfy topic (e.g., ntfy.sh/upbAfzAoFdCg99) is created that is used for all messages. Messages are "authenticated" by knowing the randomly generated topic. It is (practically speaking) as secure as a username/password combo.

To send/receive messages, you're talking about requiring a secret username/password combo that only you and Tusky know. ntfy/UnifiedPush is set up instead to require a secret topic that only you and Tusky know.

@wunter8 commented on GitHub (Jul 5, 2023): ntfy supports UnifiedPush, but it can be (and often is) used without it. When using UnifiedPush, a randomly generated ntfy topic (e.g., ntfy.sh/upbAfzAoFdCg99) is created that is used for all messages. Messages are "authenticated" by knowing the randomly generated topic. It is (practically speaking) as secure as a username/password combo. To send/receive messages, you're talking about requiring a secret username/password combo that only you and Tusky know. ntfy/UnifiedPush is set up instead to require a secret topic that only you and Tusky know.

BreizhHardware commented

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

Author

Owner

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

ntfy supports UnifiedPush, but it can be (and often is) used without it.

Why? I think UnifiedPush is the future.

When using UnifiedPush, a randomly generated ntfy topic (e.g., ntfy.sh/upbAfzAoFdCg99) is created that is used for all messages. Messages are "authenticated" by knowing the randomly generated topic. It is (practically speaking) as secure as a username/password combo.

Could we use username/password? And someone says that ntfy notifications is public?

To send/receive messages, you're talking about requiring a secret username/password combo that only you and Tusky know. ntfy/UnifiedPush is set up instead to require a secret topic that only you and Tusky know.

Do you mean the mastodon instance and ntfy? Since mastodon instance like mastodon.social sends my notifications and Tusky is only client.

@johnlpe commented on GitHub (Jul 5, 2023): > ntfy supports UnifiedPush, but it can be (and often is) used without it. Why? I think UnifiedPush is the future. > When using UnifiedPush, a randomly generated ntfy topic (e.g., ntfy.sh/upbAfzAoFdCg99) is created that is used for all messages. Messages are "authenticated" by knowing the randomly generated topic. It is (practically speaking) as secure as a username/password combo. Could we use username/password? And someone says that ntfy notifications is public? > To send/receive messages, you're talking about requiring a secret username/password combo that only you and Tusky know. ntfy/UnifiedPush is set up instead to require a secret topic that only you and Tusky know. Do you mean the mastodon instance and ntfy? Since mastodon instance like mastodon.social sends my notifications and Tusky is only client.

BreizhHardware commented

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

Author

Owner

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

Why? I think UnifiedPush is the future.

My friend. Respectfully, I think you should do a little research and find out what ntfy actually is. And maybe check your manners in the process.

Could we use username/password? And someone says that ntfy notifications is public?

The UnifiedPush spec does not support this. The endpoint is the password.

--
Side note: You have opened many tickets and tried to push your agenda on this project. I am very very receptive to suggestions, as long as it is done in a respectful way. Ultimately, as project owner, though, I get to say "no" when I want to, or I don't agree with what you'd like to do. This is an open source piece of software, so you can always fork it if you don't like that.

@binwiederhier commented on GitHub (Jul 5, 2023): > Why? I think UnifiedPush is the future. My friend. Respectfully, I think you should do a little research and find out what ntfy actually is. And maybe check your manners in the process. > Could we use username/password? And someone says that ntfy notifications is public? The UnifiedPush spec does not support this. The endpoint is the password. -- Side note: You have opened many tickets and tried to push your agenda on this project. I am very very receptive to suggestions, as long as it is done in a respectful way. Ultimately, as project owner, though, I get to say "no" when I want to, or I don't agree with what you'd like to do. This is an open source piece of software, so you can always fork it if you don't like that.

BreizhHardware commented

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

Author

Owner

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

Why? I think UnifiedPush is the future.

My friend. Respectfully, I think you should do a little research and find out what ntfy actually is.

"ntfy (pronounced notify) is a simple HTTP-based pub-sub notification service."

Yes, ntfy is publish-subscribe notification service, but is it reason to not support push notifications? And why do you think the pub-sub model is better?

You have opened many tickets and tried to push your agenda on this project. I am very very receptive to suggestions, as long as it is done in a respectful way. Ultimately, as project owner, though, I get to say "no" when I want to, or I don't agree with what you'd like to do. This is an open source piece of software, so you can always fork it if you don't like that.

Sorry if I pressed, I didn't mean to. OFC you must have able to say no.

@johnlpe commented on GitHub (Jul 9, 2023): >>Why? I think UnifiedPush is the future. > >My friend. Respectfully, I think you should do a little research and find out what ntfy actually is. "ntfy (pronounced notify) is a simple HTTP-based [_pub-sub_](https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) notification service." Yes, ntfy is publish-subscribe notification service, but is it reason to not support push notifications? And why do you think the pub-sub model is better? > You have opened many tickets and tried to push your agenda on this project. I am very very receptive to suggestions, as long as it is done in a respectful way. Ultimately, as project owner, though, I get to say "no" when I want to, or I don't agree with what you'd like to do. This is an open source piece of software, so you can always fork it if you don't like that. Sorry if I pressed, I didn't mean to. OFC you must have able to say no.

BreizhHardware referenced this issue

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

[PR #963] [MERGED] Paste images from clipboard #1477