If the push had the message it means your message was leaked to the server owner, push server owner and Apple/Google.

Until we have encrypted push messages, we have empty ones, as a security measure.

Monal (tries to) keeps a connection, so that's not the push message that you see but the actual message that Monal just got.

@joergister to expand on @licaon-kter answer - Monal (and Conversation on Android) do things a little bit differently - they also receive empty push notification, but each time they reconnect to the server to retrieve the message itself. As you noticed, Siskin doesn't do that (as it would consume more resources and doesn't seem particularly efficient). On the other hand we prefer to send encrypted push notifications (see our initial proto-XEP): https://xeps.tigase.net//docs/push-notifications/encrypt/.

You could try an account on tigase.im/sure.im to take advantage of it currently.

From what I know prosody should support this protoXEP in the future.

@joergister to expand on @licaon-kter answer - Monal (and Conversation on Android) do things a little bit differently - they also receive empty push notification, but each time they reconnect to the server to retrieve the message itself. As you noticed, Siskin doesn't do that (as it would consume more resources and doesn't seem particularly efficient). On the other hand we prefer to send encrypted push notifications (see our initial proto-XEP): https://xeps.tigase.net//docs/push-notifications/encrypt/.

Oh ok, I didn't know it was possible at all to let you connect so a server to retrieve a message (after receiving an empty push message) even if an app is closed, I always thought that was not possible due to iOS security limitations ? So no plans on your side to do it the Monal (as far as I know, not officially supported) way ? Instead if I understand it correctly, you want to do it the proper way with the new XEP you mentioned, which alas is not yet standardised and not available in the foreseeable future on the servers I mentioned due to the fact that they use ejabberd and not the Tigase server nor prosody ?

You could try an account on tigase.im/sure.im to take advantage of it currently.

Guess I'll have to do that.

Oh ok, I didn't know it was possible at all to let you connect so a server to retrieve a message (after receiving an empty push message) even if an app is closed, I always thought that was not possible due to iOS security limitations ?

It is, but there are limitations imposed by Apple so if the logging in could take a little bit longer (or Apple would change it's mind, which wouldn't be unlikely knowing Apple) then that way would fail.

So no plans on your side to do it the Monal (as far as I know, not officially supported) way ?

No, no plans as it could stop working in the future.

Instead if I understand it correctly, you want to do it the proper way with the new XEP you mentioned, which alas is not yet standardised and not available in the foreseeable future on the servers I mentioned due to the fact that they use ejabberd and not the Tigase server nor prosody ?

That's correct. Unfortunately in the context of push notifications there is no standardisation. We do hope that encrypted push would be adopted more widely.

I now have an account at sure.im but the problem is (I already uninstalled and reinstalled siskin) that the push messages can not be decrypted. I always get the push message "I sent you an OMEMO encrypted message but your client doesn’t seem to support that." as content of the push message when siskin is closed. But when I then open Siskin, the message in the chat is decrypted and perfectly readable. Push notifications are enabled and also the "When in Away/XA/DND" is enabled. Is there anything else I have to do ?

Yes, that is expected. The XMPP server is not-OMEMO aware (only clients are) and the XMPP server receives a message with body I sent you an OMEMO encrypted message but your client doesn’t seem to support that. so it sends Push Notification with this message as a payload.

Yes, that is expected. The XMPP server is not-OMEMO aware (only clients are) and the XMPP server receives a message with body I sent you an OMEMO encrypted message but your client doesn’t seem to support that. so it sends Push Notification with this message as a payload.

Ok so I thought that it would already be possible because of this comment by @woj-tek but apparrently I got it wrong.

On the other hand we prefer to send encrypted push notifications (see our initial proto-XEP): https://xeps.tigase.net//docs/push-notifications/encrypt/.

You could try an account on tigase.im/sure.im to take advantage of it currently.

So is only the server not omemo aware or is also the client not able to handle omemo encryptet push notifications yet ?

OMEMO <> Encrypted Push Notifications

Client is OMEMO aware and encrypted push notifications aware. Server is not OMEMO aware and supports encrypted push notifications.

If you would look more closely at the linked document, you would find https://xeps.tigase.net//docs/push-notifications/encrypt-omemo/ describing encrypted push notifications for OMEMO and the following statement in there:

WARNING: THIS IS A PROTOTYPE SPECIFICATION, NOT IMPLEMENTED AND NOT VALIDATED!

ah ok, though the encrypted push notifications would be omemo encrypted. So because it's just the specification that exists as of now I assume it won't be usable in the near future ?