Holger Weiß

> it's bad practice I think most admins would consider `make install` to be a "bad practice" for deploying production servers. But this all depends on your local environment and...

The [non-standard change mentioned above][1] tells ChatSecure's push service to use a different type of APNS notifications. This type has the downside that the user will only see "New Message!"...

> I send out two APNS pushes for each push iq, one foreground one background. This way there's still a chance the app will wake up in the background. Oh...

> I have plans to add this change to ejabberd's `mod_push`, but it's not done yet. It [is][1], now. [1]: https://github.com/processone/ejabberd/commit/de7dc4affa6c6996bed838b5d4b0b53511962ef0

> But most of the time, the notification text does not get replaced. I also see the case where I get *two* notifications for a single message, i.e. I then...

I see message duplication as well. This is unrelated to the sender's server. It happens when the recipient was offline while receiving messages. ChatSecure goes online and then receives the...

Deduplication of offline vs. MAM messages still doesn't work for me with build 134 (4.3.4) either. I still don't understand why messages are only classified as dups if [`foundMessage.threadId ==...

It seems Xabber also auto-responds to `type='error'` messages? A user on my server received a message from (presumably) Xabber with the following ``: > To many attempts. Try request subscription...

@ashinkarov > My proposal would be to split the events of the min loop into user-input and interface events and run them in two different threads. Why are separate threads...

> we already addressed it somewhat on our end I would think you'd need to cope with clients attempting to resume on other nodes anyway, given [the spec says][1] that...