mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #127] Feature request: android app global server url setting #107
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#107
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 @poblabs on GitHub (Feb 3, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/127
In the android app right now, the server url setting seems to be specific to UnifiedPush. It would be great if there was another global setting for the self-hosted server URL. This way you wouldn't have to enter it in under "use another server" every time you sub to a new topic. Just a thought since the "use another server" is pre-filled once you use it once.
@binwiederhier commented on GitHub (Feb 7, 2022):
So I love this idea and I did want to express that I very much agree that this should exist. Thank you for reporting it.
There's a slight "problem" though with the UX here:
The Google Play flavor only supports Firebase for ntfy.sh (a plaform limitation); plus, we have the "instant delivery" checkbox, which is only relevant for ntfy.sh, since all other hosts implicitly have instant delivery enabled.
So long story short, I don't quite know how to reconcile this in a single easy to understand dialog.
I bet I can come up with something, but it's not simple I think.
@binwiederhier commented on GitHub (Feb 13, 2022):
Let's see how hard/easy this is. I'll do this next.
@binwiederhier commented on GitHub (Feb 16, 2022):
This is done and will be in the next app release