Marvin W

@metbosch @licaon-kter These changes won't be merged as they are RFC non-compliant. The problem with metbosch's company server is that it uses a TLS certificate for jabber.company.com to claim ownership...

I am not against the option to set custom server name and port (although I won't agree with the proposed UI), however setting a custom server still requires verifying the...

You can add the flag in the sync part and write the password into it in the async part before sending the `auth` nonza. The password just has to be...

The secret service API is a [freedesktop spec](https://specifications.freedesktop.org/secret-service/), so very unlikely GNOME is going to do any changes to it without publishing an update to the spec first. And even...

- Here is a demo app of using SNI natively in Vala, so you don't need to use a library. You can just copy the code from it into Dino's...

The information could be signed using your device key, so servers can't manipulate it. However existence of an OMEMO device list is not a good indicator for if OMEMO should...

I would definitely prefer not having a bunch of header files that are not directly related to Dino in our source repository. If they can be generated at build time,...

When being called from Dino, the Cheogram SIP bridge sends a DTLS `` (in namespace `urn:xmpp:jingle:apps:dtls:0`) node with `setup="actpass"` in `transport-info`. While including a `` in `transport-info` before `session-accept` is...

I tested again with Conversations and noticed that roughly the first second of audio data sent from Cheogram is not encrypted. Cheogram basically starts sending RTP packets as soon as...

Thanks for the update. The only issue that I see now when calling from dino is that you are starting the DTLS handshake before sending the `session-accept`. Strictly speaking that's...