jdev - 2023-01-18

  1. goffi

    How is webrtc used in jingle A/V calls? The XEPs necessary are the one mentionned at https://xmpp.org/extensions/xep-0459.html#av right?

  2. MattJ

    You know this is being discussed in xsf@ right now? :)

  3. Beherit

    Mid of month - Newsletter time! ✉️ Add your news since dec 2022: https://github.com/xsf/xmpp.org/milestone/3 https://yopad.eu/p/xmpp-newsletter-365days

  4. goffi

    MattJ: yeah but it's talking about specific issues, and I don't know yet those xeps and mecanisms good enough to participate, that's why I'm asking here to not pollute the debate.

  5. MattJ

    Yeah, it's about the XEPs there

  6. edhelas

    So, when can I merge this ? https://github.com/movim/movim/pull/1128

  7. goffi

    So, it's globally the XEPs mentioned in compliance suit right? All of them are necessary (beside quality/perfs section)?

  8. goffi

    Because what I get from xsf@ is that there is a lot of obsolete stuff.

  9. MattJ

    The problem is that modern A/V stacks are quite complex, and WebRTC has "won". But XMPP is using Jingle, so there is a lot of mapping to do between the two.

  10. MattJ

    And a lot of XMPP implementations are using WebRTC, and mapping it to specific behaviour in Jingle that afaik isn't documented well or at all

  11. MattJ

    I've not worked directly on any of these implementations, so this is just my assessment of the situation

  12. goffi

    Alright thanks. And for the documented mapping, where is that mostly happening? XEP-0167 I guess? The trick is that the only reference to webrtc that I see is for datachannel in XEP-0343

  13. MattJ

    Are you planning to use WebRTC in your implementation?

  14. goffi


  15. goffi

    But I'm mostly evaluating the amount of work for now, and what is mandatory to implement and in which order, that's why I'm trying to understand it better.

  16. goffi

    Also I'm not sure if I will use only webrtc or not, will depend of the existing ecosystem I guess.