XMPP Service Operators - 2019-04-14

What's the news on when this is going to happen? https://xmpp.org/extensions/inbox/sox.html

Cuz, my development team really want to use SIP over XMPP.

Being able to self host SIP by using an XMPP account would be awesome.

I mean, this would probably work as well. https://xmpp.org/extensions/xep-0167.html

You guys already support this as well. https://xmpp.org/extensions/xep-0262.html

All that is left is https://xmpp.org/extensions/inbox/sox.html to tie it together.

How does one get a new XMPP extension approved?

Douglas Terabyte, The core specifications for XMPP are developed at the Internet Engineering Task Force (IETF) - see RFC 6120, RFC 6121, and RFC 7622 (along with a WebSocket binding defined in RFC 7395).

https://www.ietf.org/

Douglas Terabyte, https://www.ietf.org/standards/process/

Douglas Terabyte, you might find this interesting

https://diode.zone/videos/watch/8c58df50-cc22-44a3-88da-c23d5ec32bda

I did fin this interesting, thanks for the link :)

tom, Douglas Terabyte, most of the current XMPP extensions go through a standardisation process at the XSF, not at the IETF.

You can do so at the IETF too for sure, but that’s in general more for protocols which need integration with other IETF specifications, like recently XMPP over WebSocket.

Douglas Terabyte, as for SIP integration, you can already use Asterisk for instance to translate between Jingle and SIP.

There are also libraries which convert between SDP and Jingle, such as sdp-jingle-json from OTalk.

Oh! So what would it take for SoX to be a standardized XMPP extension then?

Douglas Terabyte, it seems weird to standardise SIP over XMPP while we already have Jingle which mostly every single client already supports.

Which is probably the reason it got dropped.

(Same for the plain text SDP transport XEP.)

(https://xmpp.org/extensions/inbox/jingle-sdp.html)

Also, this room is about service operators, to discuss protocols xsf@muc.xmpp.org is a lot more appropriate.

Thank you for the information and sorry if I am talking in the wrong room for this.

No problem. :)

You’re just more likely to get quality answers in the on-topic room about the protocols.

The reason why I was asking is I am working on a development group that wants to use an encrypted and decentralized platform for texting, group chats, calling, group calling, and video chatting. The best I could think of was running SIP over XMPP. That is until I learned that XMPP has it's own native system called Jingle.

You may want to have a look at Jitsi Meet, it’s an XMPP client using Jingle to do visioconference.

https://meet.jit.si/

I am also unfamiliar with XMPP's server setup and would like to learn as much as I can from your group on how to self host XMPP for my projects goals.

It uses two components on the server side to lower the bandwidth requirements in clients.

Jitsi Meet you say?

Yes.

Something looks fishy with the website

What does?

I don't know, the links to the privacy breaching social media websites. I could just be acting paranoid because this software looks too good to be true.

It is true, you can host it yourself if you want

I will share it with my group and test it out. Thanks :)

Nevermind

MattJ: https://reports.exodus-privacy.eu.org/en/reports/37219/

Can you tell me what on that page you specifically have a problem with?

Jitsi Meet uses Google CrashLytics and Google Firebase Analytics.

Douglas Terabyte, that’s just an Android application wrapper around their web code, AIUI.

You haven’t given much details about what you actually want to build, is it an Android application?

I'm trying to find or make a XMPP/SIP client to migrate my developers and other group members away from centralized and insecure platforms such as Telegram and Discord. I just want to achieve basic feature parity with what we have already been using. We need a desktop/mobile client that offers texting, calling, video chat, group chats, and group calling but all encrypted. XMPP and SIP fit the bill the best since they are literal internet protocols that can be used with any compatible client.

So are you planning on just using another service? or running your own?

Self hosting would be optimal

We are really set on using either XMPP or SIP or a combination of both protocols.

We have also considered Mumble, but it isn't as scalable as SIP and XMPP.

Sorry if I am continuing an unrelated topic to this channel.

Douglas Terabyte: not really offtopic, imho I'm playing with SIP now to some degree...

> Jitsi Meet uses Google CrashLytics and Google Firebase Analytics. That is for the android application only and through google play. You can build your own if I remember correctly.

google spyware