mastodon - Link to source

Day 2 of the Hackathon went great. Marvin (@larma) helped me implement an opt-in feature in #Conversations_im which routes all P2P sessions (calls and files transfers) via the users home server (similar to the feature found in Signal).

I went on a nice walk to a viewpoint on Mount Royal afterwards.

Now looking forward to Day 1 of #IETF124.

#XMPP #IETF #Jabber

#xmpp #Jabber #conversations_im #ietf #ietf124 @Marvin W
in reply to Goffi

mastodon - Link to source

Daniel Gultsch

@Goffi libwebrtc has a config flag for that called iceTransportsType which can be set to 'RELAY'.

I believe this is also exposed to browsers.

codeberg.org/iNPUTmice/Convers…


Conversations/src/main/java/eu/siacs/conversations/xmpp/jingle/WebRTCWrapper.java at 91ccbfe3d51b5f1c69edfb8497563a7014e36437

Conversations - Conversations is an open source XMPP/Jabber client for Android
Codeberg.org
@Goffi
in reply to Daniel Gultsch

mastodon - Link to source

Marvin W

@Goffi It's "iceTransportPolicy: relay" in RTCPeerConnection configuration in the web (see developer.mozilla.org/en-US/do…). There's also a property "force-relay" in libnice's NiceAgent. So I guess this functionality is widely available in ICE implementations.

RTCPeerConnection: RTCPeerConnection() constructor - Web APIs | MDN

The RTCPeerConnection() constructor returns a newly-created RTCPeerConnection, which represents a connection between the local device and a remote peer.
developer.mozilla.org
@Goffi
⇧