Post · bonfire.cafe

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

monal-im.org :xmpp:

@Monal@fosstodon.org replied · last month

@daniel @larma nice! Monal does this, too. Its off by default, but maybe I should turn it on by default.

Goffi

@Goffi@mastodon.social replied · last month

@Monal @daniel @larma I don't think that making it opt-out is a good idea, it would potentially put a lot of traffic to the server and make P2P nearly impossible.

Goffi

@Goffi@mastodon.social replied · last month

@daniel @larma Oh that's a nice feature. How do you do that, you just filter out ICE candidates which are local?

Marvin W

@larma@mastodon.social replied · last month

@daniel @Goffi It's "iceTransportPolicy: relay" in RTCPeerConnection configuration in the web (see https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/RTCPeerConnection#relay). 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 | MDNMDN

The RTCPeerConnection() constructor returns a newly-created RTCPeerConnection, which represents a connection between the local device and a remote peer.

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.1-alpha.8 no JS en

Automatic federation enabled