Allow finer control over UnifiedPush in the android app

[ollien]

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:

1. An option to disable UnifiedPush entirely
2. An option to block a specific app from enabling UnifiedPush
3. An option to disable instant delivery for a UnifiedPush topic

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]

(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]

/cc @S1m @karmanyaahm

[ollien]

Yeah, I am.

The offending app is Tusky. As far as I can tell there's no option for it. See this issue tuskyapp/Tusky#2692

[binwiederhier]

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]

@wunter8 Did this already.