3 ms·

> Unfortunately (or maybe fortunately), not every app uses XMPP. App doesn't need to 'use' XMPP to use push notifications. For developers, it is essentially id

> Unfortunately (or maybe fortunately), not every app uses XMPP. App doesn't need to 'use' XMPP to use push notifications. For developers, it is essentially identical to using FCM. XMPP part here simply offers a very effective way to decentralize the service, as federation server-to-server part in XMPP is wonderful, and top XMPP servers like ejabberd have great performance. > Well, please at least try to understand the thing you're criticizing before, that's the bare minimum. My company has created this very thing for a customer years ago, so I think I pretty much do understand what you are creating. It wasn't open, yet, the effort to make it open would be pretty small. We could probably release it, but I don't see the real need for it, as it is a likely dead end: making apps run in the background on Android was what we did for years, and the writing is on the wall. Background running becomes more and more difficult with each new version of Android, even on pure Android phones. Biggest manufacturers, however, like Samsung, Huawei, Xiaomi simply kill off background processes without mercy. So it is more than likely we won't be able to run 'dispatcher' apps on Android, just like we can't on iOS, and we'll have to rely solely on push notification service which is built into the phone OS. If there is a fight worth fighting, it is the one to force phone OS developers to open this part of an OS to allow using custom push notifications services.

MayeulC 4y ago
I am not trying to denigrate XMPP in any way, I also use it, though I am not very familiar with the internals. Here, the decentralized aspect doesn't seem to bring a lot of added value (what would you federate? Push senders and push servers? The relationship is mostly 1:1 in every case). > It wasn't open Then, I'm sorry, but even if the design was miles ahead of what is being proposed here, it might as well not have existed. > If there is a fight worth fighting, it is the one to force phone OS developers to open this part of an OS to allow using custom push notifications services. Well, we're proposing an API for it, and we will certainly push alternative OSes such as LineageOS, /e/ and others to adopt it; we hope it gets picked up by bigger fish, but we can't exactly pressure them into doing it, besides demonstrating that it works, documenting it and raising awareness, which is what we're doing here.

MayeulC 4y ago

I am not trying to denigrate XMPP in any way, I also use it, though I am not very familiar with the internals. Here, the decentralized aspect doesn't seem to bring a lot of added value (what would you federate? Push senders and push servers? The relationship is mostly 1:1 in every case). > It wasn't open Then, I'm sorry, but even if the design was miles ahead of what is being proposed here, it might as well not have existed. > If there is a fight worth fighting, it is the one to force phone OS developers to open this part of an OS to allow using custom push notifications services. Well, we're proposing an API for it, and we will certainly push alternative OSes such as LineageOS, /e/ and others to adopt it; we hope it gets picked up by bigger fish, but we can't exactly pressure them into doing it, besides demonstrating that it works, documenting it and raising awareness, which is what we're doing here.