@jdaviescoates said in Add UnifiedPush settings in documentation:
I could be missing something and I'm not even using the app, but just because I'd guess most people would want UnifiedPush stuff on in an app that's all about getting notified about stuff.
Unifiedpush is not used to send you notifications from Ntfy, but unifiedpush is a system that can use your ntfy server to relay notifications from apps through it, instead of using Google infrastructure for these. The list of supported software can be found at https://unifiedpush.org/users/apps/, but at least when testing this with NeoChat I not only needed give write access to up_*, but also read access.
@mononym said in Add UnifiedPush settings in documentation:
When choosing ntfy as UnifiedPush the app created some random string (i.e. the ntfy topic) and it starts with up. In the end, it is difficult to guess the topic name as it is random and as long you're not subscribed to that topic, you won't see the messages as well. Basically, write-only access is not enough to use the nfty server like a public instance as credentials are necessary to read the topic.
What I personally find difficult with Unifiedpush is giving the whole world the ability to send data (text and files) to your server. There are too many bad actors on the internet for this to be a good idea.