jdev - 2025-12-11

Out of curiosity, is there a specific MUC for GC3 discussion/development to be able to peek in on (I still have to catch up to where current progress is at)? Because I also have some side project idea of a multi-protocol bridged MUC system, and not sure if there's any improvements or regressions with GC3 that could make it better/worse

There's a MUC but not a tonne of activity since everyone is busy.

It's all small changes though. No IQ to participant full jids by default. MUC full jids with occupant ids instead of nicknames. A single IQ to get all affiliations instead of 4. Things like that

Sounds useful, just worried at the "full jids" part, if that'll complicate some things with bridged users, where the bridging is done inside the MUC service rather than a separate component entirely for each protocol

Has XEP-0430 (Inbox) been implemented anywhere?

For people who have integrated Tor in their client, what do you do with webRTC? Do you simply forbid A/V calls and file transfer via WebRTC? Tor browser disables it. ✏

I disable it, or utilize Dino for A/V.

Schimon, I'm talking about using XMPP over Tor.

I was answering about XMPP over Tor with han HTML browser.

Schimon, I'm talking about using Tor in a regular client (i.e. not a webclient via Tor browser). I don't see what Dino has to do here. My question is for people who did the implementation, because. WebRTC leaks IP, so I'm wondering if they simply disable it, or if there is another way. ✏

you can tell it to only advertise TURN IPs I think

> Schimon, I'm talking about using Tor in a regular client (i.e. not a webclient via Tor browser). I don't see what Dino has to do here. My question is for people who did the implementation, because. WebRTC leaks IP, so I'm wondering if they simply disable it, or if there is another way. I did not knoow of that issue. ↺

> I did not knoow of that issue. no worries. ↺

> you can tell it to only advertise TURN IPs I think I'm trying to think how it could work. The TURN must advertise an IP going through Tor, so we would have somehow to tell webRTC to use local Tor daemon as Proxy. If we can do that, there is not really a point in using TURN, is there? ↺

I'm checking GStreamer doc, we can use HTTP proxy for turn: https://gstreamer.freedesktop.org/documentation/webrtc/index.html?gi-language=python#webrtcbin:http-proxy . So this could be Tor, but I'm not sure how to make the server advertise a Tor IP or domain. At least, this seems like an option on the client side to use WebRTC without leaking IP.

On the server it seems that I can simply advertise a onion domain. That looks like an option, thanks moparisthebest.