Hacker News new | past | comments | ask | show | jobs | submit login

Can you self-host whatever it takes to handle push notification yourself?



Docs here: https://zulip.readthedocs.io/en/stable/production/mobile-pus...

In short, you have to change some config in the self-hosted Zulip server, and publish modified versions of the application to the app stores you want to support. This is not a limitation of Zulip, it's the app stores forcing all apps to have their notification sources restricted to a common, known ahead of time, server.


As I wrote under another comment, this doesn't seem like a good reason or I must be missing something because I can selfhost Matrix or an XMPP server and get notifications for free with any client.

Whatever Zulip is offering here is not good and if these other offerings can make it free, Zulip should be able to too without charge or requiring I recompile their app.


The Element client will register your client with their push notification system (even if self hosted). It will attach data to your session on your homeserver of where the homeserver should send notifications of new messages for APNS, FireBase, or UnifiedPush. The respective notification pipeline will wake up your device, and inform Element of the new messages, and display them accordingly on your device.

Android + Apple OS only listen to their respective ecosystem's push notification system, in order to minimize battery drain + needed background services on their phones.

Element has a push server to send to Apple + Google's offerings:

https://ems-docs.element.io/books/element-support/page/under...

You can configure Element to use ntfy, or some other unifiedpush implementation, but (a) this is hopeless on stock iOS devices since apple severely limits what background services can do (b) this is frustrating on Android because there is inconsistent handling of background services.

Since I use android, I've taken option (b), and it's worked mostly okay, because I've figured out the specific magic spell for my OnePlus phone to leave the background ntfy service alone, and I'm willing to eat the extra battery to have one more service running in the background.


Isn't that pull notification instead of push?


> As I wrote under another comment, this doesn't seem like a good reason or I must be missing something because I can selfhost Matrix or an XMPP server and get notifications for free with any client.

I don't know about Matrix, but for XMPP, push notifications work like this:

XMPP Client tells the XMPP server where to send push notifications to (a server controlled by the client author); the XMPP server sends notifications there; the server connects with an API key to Google or Apple for the push notification to appear on your phone.

Presumably the cost of running a server is low enough that free Matrix and XMPP apps exist. It's definitely not free.

Zulip is charging to nudge businesses into using their paid version. It's their server that they are running, so they are free to do so. Your Matrix and/or XMPP client is choosing to not charge, which they are also free to do so.

Zulip provides instructions on how to use a different notification server; if you want to avoid giving them money that much, then you can do so.


It sounds like if you want to use the official mobile apps they can only receive notifications from Zulip's service so you can't run your own.


seems like you can but you need to recompile the mobile apps.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: