[GH-ISSUE #1484] . #1049

New issue

Closed

opened 2026-05-07 00:29:51 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-07 00:29:51 +02:00

Owner

Originally created by @ghost on GitHub (Nov 8, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1484

Originally created by @ghost on GitHub (Nov 8, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1484

BreizhHardware

2026-05-07 00:29:51 +02:00

closed this issue
added the
question
label

BreizhHardware commented

2026-05-07 00:29:52 +02:00

Author

Owner

@wunter8 commented on GitHub (Nov 8, 2025):

I don't think releasing that feature would cause any problems. Each IP address that sends messages to the public ntfy.sh instance is limited to 250 published messages/day. So as long as devices aren't waking up and sending messages more frequently than that, it shouldn't be an issue.

To make things a bit easier for your users, if you put a clickable link somewhere in your app that matches this format, then users can click on it to automatically subscribe to their user device topic in the ntfy Android app: ntfy://topic

Each device ID is globally unique, right? Since all the topics are public and using the same ntfy.sh server, devices with the same IDs would cause conflicts.

For the future, since ntfy is self-hostable, and since there's probably a lot of overlap between syncthing users and ntfy users, you might consider letting your users configure which ntfy.sh server they are publishing messages to.

@wunter8 commented on GitHub (Nov 8, 2025): I don't think releasing that feature would cause any problems. Each IP address that sends messages to the public ntfy.sh instance is limited to 250 published messages/day. So as long as devices aren't waking up and sending messages more frequently than that, it shouldn't be an issue. To make things a bit easier for your users, if you put a clickable link somewhere in your app that matches this format, then users can click on it to automatically subscribe to their user device topic in the ntfy Android app: `ntfy://topic` Each device ID is globally unique, right? Since all the topics are public and using the same ntfy.sh server, devices with the same IDs would cause conflicts. For the future, since ntfy is self-hostable, and since there's probably a lot of overlap between syncthing users and ntfy users, you might consider letting your users configure which ntfy.sh server they are publishing messages to.

BreizhHardware commented

2026-05-07 00:29:52 +02:00

Author

Owner

@wunter8 commented on GitHub (Nov 8, 2025):

I think the commit you just pushed should be fine. Most ntfy server URLs are of the format https://ntfy.domain.com but something like http://192.168.0.123:8080 is also valid (assuming a ntfy server is actually listening on that IP address and port)

@wunter8 commented on GitHub (Nov 8, 2025): I think the commit you just pushed should be fine. Most ntfy server URLs are of the format `https://ntfy.domain.com` but something like `http://192.168.0.123:8080` is also valid (assuming a ntfy server is actually listening on that IP address and port)

BreizhHardware commented

2026-05-07 00:29:52 +02:00

Author

Owner

@wunter8 commented on GitHub (Nov 9, 2025):

Sorry. I had the format wrong: https://docs.ntfy.sh/subscribe/phone/#ntfy-links

It needs to be ntfy://host/topic. So something like ntfy://ntfy.sh/device-id

Let me know if that's still not working

@wunter8 commented on GitHub (Nov 9, 2025): Sorry. I had the format wrong: https://docs.ntfy.sh/subscribe/phone/#ntfy-links It needs to be `ntfy://host/topic`. So something like `ntfy://ntfy.sh/device-id` Let me know if that's still not working

BreizhHardware referenced this issue

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

[PR #1049] [MERGED] Remove Rate-Topics #1501