@ilpianista Thanks for catching that up - we will look into it.
@Muto We shouldn't aim at "compatibility with conversation" but rather "compatibility with XMPP" - with the former we are heading in a quite iffy territory, vide recent publication from Monal developer: https://monal.im/blog/omemo-is-broken-in-general-across-the-ecosystem/
PS. I'm not that sure that "majority of XMPP users are conversations users" - definitely they are significant group :-)
@stevenroose we just upgrade our instance - I checked from our end and connection to your server worker OK. Could you please check if notifications work for you now? (toggling off-on may be required in the app though)
As for OTR/OMEMO - given that #BeagleIM and #SiskinIM are quite young we opted for implementation of the most popular e2e out there (a bit of "due to popular demand"). However, in the future, we will most lean towards MLS instead of OTR.
@stevenroose It looks ok and our local test shows that it should work after upgrade.
As for the room - there is general muc firstname.lastname@example.org (but given above issue you may have problem accessing it -- we know sasl-external is pressing matter!)
@liaizon Were it able to connect to the server? Regular messages or push?
@ij We'd report that as something that should be corrected.
@ij Why would it return code == 200 if the specification explicitly mentiones code 201?
@zerok Any particular hints that could us improve? (I'm aware that you said you intended to submit some issues but decided on skipping on that…)
@aperalesf deberían aparecer automáticamente en la aplicación. Desafortunadamente modo de operación es muy parecido a Chatsecure - al conectar entras a todas las salas de charla.
One of the top real-time communication software providers.
We like to make things to scale, in fact we are little bit too obsessed with optimizations.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!