Android provides a mechanism for marking a service, receiver, or provider to only run on user 0 and for all requests to that service, receiver, or provider to be routed to the one on user 0 rather than within the current user [1].
If ntfy was to take advantage of this, users who segregate their apps between user profiles (as is common with GrapheneOS for example) would be able to still keep one ntfy instance locally and one connection back to the ntfy server rather than requiring one instance per user.
I may be able to eventually try writing up a PR implementing this functionality but it'll likely be a decent while before I do so.
Android provides a mechanism for marking a service, receiver, or provider to only run on user 0 and for all requests to that service, receiver, or provider to be routed to the one on user 0 rather than within the current user [1].
If ntfy was to take advantage of this, users who segregate their apps between user profiles (as is common with GrapheneOS for example) would be able to still keep one ntfy instance locally and one connection back to the ntfy server rather than requiring one instance per user.
I may be able to eventually try writing up a PR implementing this functionality but it'll likely be a decent while before I do so.