Richard Bayerle

Sorry, I just saw that the last reply is by me and was done quite some time ago. Since you still run into the issue, I'll reopen this one (though...

hi @Flamefire, sorry for not replying earlier. i agree, the build definitely got too complicated for a makefile, especially now. thanks for the pointers on which cmake functionality to make...

Well, XMPP is very finnicky. If the devicelist is empty, that's correct behaviour. I assume the other clients keep the devicelist around for some time so they don't run into...

>So your theory is, the converse.js client would fail to publish the devicelist and the other working client running conversation has the devicelist cached and is using that. No, my...

Sorry, I lost track of this. >(maybe) whenever a contact comes online (might be dangerous?) This is actually how PEP works. There should be an update from your contact when...

hi @root-hardenedvault, thanks again for the contribution. thanks, good catch, in retrospect i don't know what i was thinking just replacing the value behind the pointer without freeing anything. i...

I switched off sending an additional `` like this because ChatSecure can't handle those (see [here](https://github.com/ChatSecure/ChatSecure-iOS/issues/717)). Instead, I send an [EME](https://xmpp.org/extensions/xep-0380.html) element, and as far as I know, Conversations switched...

I was just trying to say that there is in fact a message to notify clients, it just isn't parsed because the clients don't support that XEP. If I do...

You are saying working around noncompliance is not a good solution, but all the other people asking me why they cannot talk to ChatSecure don't. I think it's a very...

Sorry for not replying, I failed to tell you how much I appreciate your contribution. As you can see on the dev branch, I was quite busy with something else....