Stephen Paul Weber

@mattchrist I believe I have resolved all the currently-requested changes

If the main issue is that the binary from Maven is not longer sufficient, I am hosting a content-addressable version of the latest WebRTC that can be used like this:...

>Anyone can build it, not the issue. Except that almost no CI can build it due to size constraints. >Building it from FOSS only deps (not from 20Gb of binaries...

@licaon-kter Sorry, I just meant since the build was using a binary from Maven before, maybe a stable binary could be used now and the situation would not be worse....

"Jabber ID" is the correct full name used in all XMPP documentation. I agree that the full name is less ambiguous than "JID".

> AFAIK there is no threading support (at least not widespread) for XMPP. Threading support is actually baked right into the base standard, and is supported in a basic way...

We are keen to figure this out. We have spent some time in attempting to debug it, but have not come up with a conclusion yet. Note that calls work...

> For calls started from my test SIP client to Dino, Audio is currently only going from SIP to Dino and not the other way round. We have had some...

Is this the same problem as #745 ? I also happily use MAM with other clients, but with Xabber it says my prosody server has no MAM...

I am now using dino as my main IM client on pinephone (under sxmo / postmarketOS). It works pretty great as-is, though it has a papercut that I cannot close...