mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #883] Nested topics possible? ie: my-topic/group1 or my-topic/group2 #625
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#625
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ktiedt on GitHub (Sep 15, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/883
❓ Question
I have done some testing with this and it appears to not be supported, however, I wanted to make sure so I am asking here. I was testing to see if topics could be nested, like so 'mytopic/group1' 'mytopic/group2' so that one main topic name works for the entire application, and all the specific topics would live under it, and could be subscribed to specifically, or retrieved as a sub to 'mytopic' and hear everything. Currently the IOS app wont even allow 'mytopic/extra' to be added, but also, no topics were found online or in the issues that seemed to match.
And just to be thorough, in this example, listening to 'mytopic/group1' would only see pubs for 'mytopic-group1', same for group2, but something listening to 'mytopic' would recieve notifications of both 'mytopic/group1' and 'mytopic/group2'
Thanks in advance and thanks for the awesome project.
@wunter8 commented on GitHub (Sep 15, 2023):
This is not supported right now, and there aren't any plans to add it
You could achieve something similar (at least through the API) using tags: https://docs.ntfy.sh/subscribe/api/#filter-messages
As far as I know, neither Android or iOS supports filtering by tags yet, though
@ktiedt commented on GitHub (Sep 15, 2023):
Thanks @wunter8 i suppose tags would not be useful for access restrictions based on that response as well so sounds like a non-starter for this design. Back to the drawing board for me.
@wunter8 commented on GitHub (Sep 16, 2023):
ntfy has other features for access restrictions (See access control in the docs)
What are you trying to set up? It might not be quite as convenient, but devices could just subscribe to one or more of the topics
mytopic,mytopic-group1, andmytopic-group2, and the publishing device can choose which topic is appropriate to publish to, right?@ktiedt commented on GitHub (Sep 16, 2023):
@wunter8 something akin to user based subscriptions without having to create a new topic for every event type and maintain access control so only said user or admins could view them. Examples:
Mytopic/user1/on-message
Vs
Mytopic/user2/on-message
Cheesy example but easiest I could think of without going into the weeds
@binwiederhier commented on GitHub (Sep 24, 2023):
As @wunter8 said, there are no plans for subtopic support. You can achieve user access for "subtopics only accessible for ..." using ACLs and patterns, e.g. `ntfy access user1 'mytopic-group1-*', but that's all. I think it's still limited and won't wor for your entire use case, though.
I'm closing this ticket since it's about nested topics, but feel free to continue talking here or on Discord/Matrix.