mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #646] Allow finer control over UnifiedPush in the android app #479
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#479
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 @ollien on GitHub (Mar 2, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/646
Right now, if an app wants to use UnifiedPush, it can simply register itself. This causes ntfy to use instant delivery, which makes sense given the usecase of UnifiedPush, but is a bit frustrating if you only wanted to use ntfy for other pushes and don't want the battery drain of instant delivery.
Ideas for possible controls:
I don't know how the project feels about any of these, but I imagine that #1 is perhaps the "easiest" (said without much context).
@binwiederhier commented on GitHub (Mar 3, 2023):
(I am assuming that you are talking about the Android app)
I used to have a toggle in the Settings that allowed disabling UnifiedPush entirely, but I removed that because I didn't want toggle-hell. I haven't heard this argument before, to be honest. Usually you can choose the notification method in the app itself and unselect "ntfy" there. What app is misbehaving and registering itself without your consent?
@binwiederhier commented on GitHub (Mar 3, 2023):
/cc @S1m @karmanyaahm
@ollien commented on GitHub (Mar 3, 2023):
Yeah, I am.
The offending app is Tusky. As far as I can tell there's no option for it. See this issue https://github.com/tuskyapp/Tusky/issues/2692
@binwiederhier commented on GitHub (Mar 3, 2023):
I'd be ok with an off switch for UP if somebody wants to implement it (cough, @wunter8, maybe?). That said, it does seem like a Tusky issue.
@binwiederhier commented on GitHub (Mar 7, 2023):
@wunter8 Did this already.