5 ms·

> It looks like you have integrated with firebase Unfortunately, Firebase requires Google services. UnifiedPush integration would be nice

binwiederhier 5y ago
1. The F-Droid flavor of the app [1] does not require or use Firebase. And: If you self-host the server and use the Google Play flavor [2] of the app, it won't use Firebase either. 2. I've just started work [3] on making ntfy a UnifiedPush (https://unifiedpush.org https://unifiedpush.org) distributor, meaning that other apps/services will be able to use ntfy.sh (or a self-hosted server) as a means to deliver notifications or messages. I'm super excited about this, and I don't think it'll take very long. [1] https://f-droid.org/en/packages/io.heckel.ntfy/ https://f-droid.org/en/packages/io.heckel.ntfy/ [2] https://play.google.com/store/apps/details?id=io.heckel.ntfy https://play.google.com/store/apps/details?id=io.heckel.ntfy [3] https://github.com/binwiederhier/ntfy/issues/9 https://github.com/binwiederhier/ntfy/issues/9
- resonator 5y ago
  I look forward to that. I wouldn't try it without unified push but if you add that, it could be easily be better than gotify which really only provides the bare minimum.
- stavros 5y ago
  Hmm, I'm not very well versed in Android push messaging, but how does your self-hosted binary send notifications? Don't you need to include GCM keys somewhere?
  - binwiederhier 5y ago
    If you self-host, FCM is not involved at all. The app will run a foreground service which keeps a connection to your selfhosted server open. I detailed it a bit more here with links to the docs: https://news.ycombinator.com/item?id=29719493 https://news.ycombinator.com/item?id=29719493 Edit: If you want to use FCM for your selfhosted server, you can, but you have to build your own .APK file. Instructions are here: https://ntfy.sh/docs/develop/#android-app https://ntfy.sh/docs/develop/#android-app
    - stavros 5y ago
      Ahh, thanks, that clarifies things! One feature request I had was to use encryption so FCM can't read your notifications, but that might not be what your service is for.
      - binwiederhier 5y ago
        I've been thinking about adding it for the Android app and the CLI as an option, but then using it with curl isn't possible anymore. I created a ticket to remind myself: https://github.com/binwiederhier/ntfy/issues/69 https://github.com/binwiederhier/ntfy/issues/69 Feel free to add your hopes and dreams to the ticket. ;-)
    - throw14082020 5y ago
      A "foreground service" means 2 things: an unremovable notification is shown to the user in their notification tray AND specifically for ntfy, an additional connection open (additional battery usage) on top of the one engineered by Google. Although I like seeing things attempt to compete with Google, this can't come close because of the restrictions of Android enacted by Google.
      - binwiederhier 5y ago
        Yes, sadly Google/Android makes it impossible to do it in a battery efficient manner. UnifiedPush [1] is attempting to create a competitive mechanism that apps can use and share for notifications and server-to-device messages. There is still one open connection, but it can be shared by all apps on the phone. I have recently started work to make ntfy a UnifiedPush distributor [2]. Side note: - you _can_ actually dismiss the foreground service notification, see [3] for a screenshot - the battery impact is not as severe as I had thought initially. On my phone, it's about 4% battery over 17h "use" [4]. I'm planning on making "slow delivery" possible to counter this bahavior, see this ticket [5] [1] https://unifiedpush.org https://unifiedpush.org [2] https://github.com/binwiederhier/ntfy/issues/9 https://github.com/binwiederhier/ntfy/issues/9 [3] https://ntfy.sh/docs/subscribe/phone/#instant-delivery https://ntfy.sh/docs/subscribe/phone/#instant-delivery [4] https://ntfy.sh/docs/faq/#how-much-battery-does-the-android-app-use https://ntfy.sh/docs/faq/#how-much-battery-does-the-android-... [5] https://github.com/binwiederhier/ntfy/issues/32 https://github.com/binwiederhier/ntfy/issues/32

binwiederhier 5y ago

1. The F-Droid flavor of the app [1] does not require or use Firebase. And: If you self-host the server and use the Google Play flavor [2] of the app, it won't use Firebase either. 2. I've just started work [3] on making ntfy a UnifiedPush (https://unifiedpush.org https://unifiedpush.org) distributor, meaning that other apps/services will be able to use ntfy.sh (or a self-hosted server) as a means to deliver notifications or messages. I'm super excited about this, and I don't think it'll take very long. [1] https://f-droid.org/en/packages/io.heckel.ntfy/ https://f-droid.org/en/packages/io.heckel.ntfy/ [2] https://play.google.com/store/apps/details?id=io.heckel.ntfy https://play.google.com/store/apps/details?id=io.heckel.ntfy [3] https://github.com/binwiederhier/ntfy/issues/9 https://github.com/binwiederhier/ntfy/issues/9

resonator 5y ago
I look forward to that. I wouldn't try it without unified push but if you add that, it could be easily be better than gotify which really only provides the bare minimum.
stavros 5y ago
Hmm, I'm not very well versed in Android push messaging, but how does your self-hosted binary send notifications? Don't you need to include GCM keys somewhere?
- binwiederhier 5y ago
  If you self-host, FCM is not involved at all. The app will run a foreground service which keeps a connection to your selfhosted server open. I detailed it a bit more here with links to the docs: https://news.ycombinator.com/item?id=29719493 https://news.ycombinator.com/item?id=29719493 Edit: If you want to use FCM for your selfhosted server, you can, but you have to build your own .APK file. Instructions are here: https://ntfy.sh/docs/develop/#android-app https://ntfy.sh/docs/develop/#android-app
  - stavros 5y ago
    Ahh, thanks, that clarifies things! One feature request I had was to use encryption so FCM can't read your notifications, but that might not be what your service is for.
    - binwiederhier 5y ago
      I've been thinking about adding it for the Android app and the CLI as an option, but then using it with curl isn't possible anymore. I created a ticket to remind myself: https://github.com/binwiederhier/ntfy/issues/69 https://github.com/binwiederhier/ntfy/issues/69 Feel free to add your hopes and dreams to the ticket. ;-)
  - throw14082020 5y ago
    A "foreground service" means 2 things: an unremovable notification is shown to the user in their notification tray AND specifically for ntfy, an additional connection open (additional battery usage) on top of the one engineered by Google. Although I like seeing things attempt to compete with Google, this can't come close because of the restrictions of Android enacted by Google.
    - binwiederhier 5y ago
      Yes, sadly Google/Android makes it impossible to do it in a battery efficient manner. UnifiedPush [1] is attempting to create a competitive mechanism that apps can use and share for notifications and server-to-device messages. There is still one open connection, but it can be shared by all apps on the phone. I have recently started work to make ntfy a UnifiedPush distributor [2]. Side note: - you _can_ actually dismiss the foreground service notification, see [3] for a screenshot - the battery impact is not as severe as I had thought initially. On my phone, it's about 4% battery over 17h "use" [4]. I'm planning on making "slow delivery" possible to counter this bahavior, see this ticket [5] [1] https://unifiedpush.org https://unifiedpush.org [2] https://github.com/binwiederhier/ntfy/issues/9 https://github.com/binwiederhier/ntfy/issues/9 [3] https://ntfy.sh/docs/subscribe/phone/#instant-delivery https://ntfy.sh/docs/subscribe/phone/#instant-delivery [4] https://ntfy.sh/docs/faq/#how-much-battery-does-the-android-app-use https://ntfy.sh/docs/faq/#how-much-battery-does-the-android-... [5] https://github.com/binwiederhier/ntfy/issues/32 https://github.com/binwiederhier/ntfy/issues/32