New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Friendly names for servers in notifications #1059
Comments
This already exists in the web app and android app. (It's implemented similar to option 1). Not sure when we'll get it added to the iOS app, but it's on the list! |
You mention title of notifications in your original message. I did see the server name in the notification on iOS initially and though that it didn't look great but I then realised that this is only there as default when no title is defined. Have you set a title for your messages using |
I would love to see that feature in the iOS app, too. A suggestion: Maybe you could move the domain into a new grey subtitle line, above the notifications count, and have the topic itself the only thing in the list title. Thank you for that great app and project 馃槉 |
馃挕 Idea
I think it would be convenient to have the ability to create aliases (or friendly names) for ntfy servers. Not all of the places that I host my ntfy servers have human friendly domain/subdomains. The title of the notifications that I receive have pretty long domains and make it hard to find where the topic name is at the end.
馃捇 Target components
I'm not a mobile app developer (and I only have iOS devices) so I have no idea how much work it would be to modify the content included in the title of the notifications. I think there are two options for how I could see it implemented. Option 1: when adding the subscription to the mobile app, there's a textbook for a friendly name that overwrites the domain in the title of the notification for that topic. Option 2: adding a config parameter for a friendly name that is included when publishing notifications and overwrites the domain in the title of the notification. Both options would alleviate my concern.
Love the work you've done with this project!
The text was updated successfully, but these errors were encountered: