3 ms·

> XEP-0357 from 2015 Taking a quick look, this one is marked deferred; I don't know what that means, but it sounds like it's not an accepted standard?. It requ

by toast0 21d ago

> XEP-0357 from 2015 Taking a quick look, this one is marked deferred; I don't know what that means, but it sounds like it's not an accepted standard?. It requires the application push server to be an XMPP server (which I suspect is challenging for client developers, compared to having a https url that takes a POST or similar) and doesn't include a method for a client to request a test push to validate the setup or discuss feedback to the client for push failure. This doesn't feel solved to me. I didn't review XEP-0198 closely, based on perhipheral ecosystem interaction, I do think that one is solved.

wahern 21d ago
Both Monal and Conversations support XEP-0357. Each project runs their own XMPP-to-Apple/Google gateway for push notifications. It has to be that way because the gateway server and client phone application have to be signed by the same developer account. The client phone app tells your XMPP server which gateway to use (or maybe it's vice-versa, the gateway contacts your server. I forget). In any event XMPP servers like Prosody support this out-of-the-box.
deleted 20d ago
[deleted]