[GH-ISSUE #689] Use @ to define a server #507

New issue

Closed

opened 2026-05-07 00:24:53 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

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

Owner

Originally created by @adriy-be on GitHub (Mar 29, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/689

💡 Idea
Hi, I think adding the possibility to put the server in the topic name can make the configuration easier. An example mytopic@myserver.net

💻 Target components
Android app, iOS app, web app

Originally created by @adriy-be on GitHub (Mar 29, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/689 :bulb: **Idea** Hi, I think adding the possibility to put the server in the topic name can make the configuration easier. An example mytopic@myserver.net :computer: **Target components** Android app, iOS app, web app

BreizhHardware

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

closed this issue
added the
enhancement
label

BreizhHardware commented

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

Author

Owner

@adriy-be commented on GitHub (Mar 29, 2023):

I have no experience with kotlin, but I just saw the application code.
I think it can be easy to implement, there is already a splitTopicUrl function, this function doesn't use '@' but '/'.

Without this character, the default server is chosen, otherwise the custom is used.

@adriy-be commented on GitHub (Mar 29, 2023): I have no experience with kotlin, but I just saw the application code. I think it can be easy to implement, there is already a splitTopicUrl function, this function doesn't use '@' but '/'. Without this character, the default server is chosen, otherwise the custom is used.

BreizhHardware commented

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

Author

Owner

@binwiederhier commented on GitHub (Mar 31, 2023):

Thank you for your suggestion! Seems like a good thought, but I do think it's a little more complicated.

This seems to be a feature request that is solely around the aesthetics of the topic URL. The base URL and topic URL logic has been around since the very beginning, so I am pretty sure that changing it would not be easy at all. Especially since there are many clients (web, iOS, Android, third party).

On top of that, having an email-style topic identifier would

make it impossible to distinguish between HTTP and HTTPS base URLs
would likely confuse people, because they'd think they can email to the topic (which they can, sometimes, but not necessarily to your suggested scheme)

All in all, I think it may confuse people more and is IMHO not worth the effort.

@binwiederhier commented on GitHub (Mar 31, 2023): Thank you for your suggestion! Seems like a good thought, but I do think it's a little more complicated. This seems to be a feature request that is solely around the aesthetics of the topic URL. The base URL and topic URL logic has been around since the very beginning, so I am pretty sure that changing it would not be easy at all. Especially since there are many clients (web, iOS, Android, third party). On top of that, having an email-style topic identifier would - make it impossible to distinguish between HTTP and HTTPS base URLs - would likely confuse people, because they'd think they can email to the topic (which they can, sometimes, but not necessarily to your suggested scheme) All in all, I think it may confuse people more and is IMHO not worth the effort.

BreizhHardware referenced this issue

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

[GH-ISSUE #1680] INPUT WANTED: iOS improvement plan 🍎📱 #1170