[GH-ISSUE #1215] Randomly generate topic/password when publishing a message #858

Open
opened 2026-05-07 00:28:13 +02:00 by BreizhHardware · 0 comments

Originally created by @tentme on GitHub (Nov 3, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1215

💡 Idea

This differs from randomly generating a topic name via the web UI; in this case, the topic name is generated during the publishing process. For example, when you curl -d "test" ntfy.sh/ (to the baseurl), the server will respond with something like:
{"id":"$random_id","time":$timestamp,"expires":$anothertimestamp,"event":"message","topic":"$randomly_generated_topic_name","message":"test"} So users don't have to pick the password themselves.

I'm new to ntfy, so I'm not sure if this already exists since the idea seems obvious. Please feel free to close this issue if it is already implemented or has been considered and confirmed not to be developed.

Originally created by @tentme on GitHub (Nov 3, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1215 :bulb: **Idea** This differs from randomly generating a topic name via the web UI; in this case, the topic name is generated during the publishing process. For example, when you `curl -d "test" ntfy.sh/` (to the `baseurl`), the server will respond with something like: `{"id":"$random_id","time":$timestamp,"expires":$anothertimestamp,"event":"message","topic":"$randomly_generated_topic_name","message":"test"}` So users don't have to pick the password themselves. I'm new to ntfy, so I'm not sure if this already exists since the idea seems obvious. Please feel free to close this issue if it is already implemented or has been considered and confirmed not to be developed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#858
No description provided.