|
|
@@ -11,17 +11,16 @@ the service.
|
|
|
Best effort.
|
|
|
|
|
|
## What happens if there are multiple subscribers to the same topic?
|
|
|
-As per usual with pub-sub, all subscribers receive notifications if they are
|
|
|
-subscribed to a topic.
|
|
|
+As per usual with pub-sub, all subscribers receive notifications if they are subscribed to a topic.
|
|
|
|
|
|
## Will you know what topics exist, can you spy on me?
|
|
|
-If you don't trust me or your messages are sensitive, run your own server. It's <a href="https://github.com/binwiederhier/ntfy">open source</a>.
|
|
|
-That said, the logs do not contain any topic names or other details about you.
|
|
|
-Messages are cached for the duration configured in `server.yml` (12h by default) to facilitate service restarts, message polling and to overcome
|
|
|
-client network disruptions.
|
|
|
+If you don't trust me or your messages are sensitive, run your own server. It's open source.
|
|
|
+That said, the logs do contain topic names and IP addresses, but I don't use them for anything other than
|
|
|
+troubleshooting and rate limiting. Messages are cached for the duration configured in `server.yml` (12h by default)
|
|
|
+to facilitate service restarts, message polling and to overcome client network disruptions.
|
|
|
|
|
|
## Can I self-host it?
|
|
|
-Yes. The server (including this Web UI) can be self-hosted, and the Android app supports adding topics from
|
|
|
+Yes. The server (including this Web UI) can be self-hosted, and the Android/iOS app supports adding topics from
|
|
|
your own server as well. Check out the [install instructions](install.md).
|
|
|
|
|
|
## Why is Firebase used?
|
|
|
@@ -34,16 +33,12 @@ of the app and [self-host your own ntfy server](install.md).
|
|
|
|
|
|
## How much battery does the Android app use?
|
|
|
If you use the ntfy.sh server, and you don't use the [instant delivery](subscribe/phone.md#instant-delivery) feature,
|
|
|
-the Android app uses no additional battery, since Firebase Cloud Messaging (FCM) is used. If you use your own server,
|
|
|
-or you use *instant delivery*, the app has to maintain a constant connection to the server, which consumes about 0-1% of
|
|
|
-battery in 17h of use (on my phone). There has been a ton of testing and improvement around this. I think it's pretty
|
|
|
+the Android/iOS app uses no additional battery, since Firebase Cloud Messaging (FCM) is used. If you use your own server,
|
|
|
+or you use *instant delivery* (Android only), the app has to maintain a constant connection to the server, which consumes
|
|
|
+about 0-1% of battery in 17h of use (on my phone). There has been a ton of testing and improvement around this. I think it's pretty
|
|
|
decent now.
|
|
|
|
|
|
## What is instant delivery?
|
|
|
[Instant delivery](subscribe/phone.md#instant-delivery) is a feature in the Android app. If turned on, the app maintains a constant connection to the
|
|
|
-server and listens for incoming notifications. This consumes <a href="#battery-usage">additional battery</a>,
|
|
|
+server and listens for incoming notifications. This consumes additional battery (see above),
|
|
|
but delivers notifications instantly.
|
|
|
-
|
|
|
-## Why is there no iOS app (yet)?
|
|
|
-I don't have an iPhone or a Mac, so I didn't make an iOS app yet. It'd be awesome if
|
|
|
-<a href="https://github.com/binwiederhier/ntfy/issues/4">someone else could help out</a>.
|
Philipp Heckel