XSF Discussion - 2013-11-26


  1. Kev

    Does anyone have a link to the minutes for last week's meeting? I can't find them.

  2. Kev

    Or were they only sent to the board@ list?

  3. fippo

    cant find them either...

  4. dwd

    https://fund.arkos.io/ -- Instant server, just add Raspberry Pi. Note that it includes a turnkey XMPP server.

  5. SouL

    yep

  6. dwd

    Is anyone involved with them already?

  7. dwd

    And does anyone know which XMPP server they (are intending to) use?

  8. Zash

    Freedombox?

  9. SouL

    I follow someguy at Diaspora* that knows something about arkos, I'll ask that.

  10. ralphm

    From an initial search, my guess is that it would be Prosody.

  11. Zash

    \o/

  12. ralphm

    I think that contributing to this ticket will make that more likely: https://github.com/cznweb/genesis/issues/32

  13. Kev

    Is it Monday or Tuesday in London?

  14. Kev

    Monday, nvm.

  15. MattJ

    It's the same day as the rest of the UK, Tuesday

  16. MattJ

    But while typing, I realised what you meant

  17. Kev

    Looks like I might be able to make it after all.

  18. Lloyd

    We've moved the event BTW. Now going to be at Shoreditch works, we're tacking on to the end of an IoT conference so will be a good opportunity for XMPP to get more exposure in that space.

  19. Kev

    Ah.

  20. Kev

    Got an address?

  21. Lloyd

    http://shoreditchworks.com <http://shoreditchworks.com/>

  22. Lloyd

    Its the "Village hall"

  23. Kev

    Ta.

  24. Lloyd

    We're on the end of http://redmonk.com/thingmonk/ which is a practical IoT hacking conf.

  25. Kev

    Time?

  26. Lloyd

    Any time after the end of the conf as there'll be people around 6pm+

  27. Kev

    Assuming I'm not going to be able to turn up until 7ish at best, is there any point doing so, or will you all have gone home by then? :)

  28. Kev

    Over an hour and a half from the office - yikes.

  29. Kev

    I guess that means I'm not likely to be able to make it much before 19:30.

  30. Lloyd

    That's fine, we won't really get started until 7pm, and the first bit is probably me or Steffen doing an XMPP intro

  31. Lloyd

    I think you could potentially get away with skipping the intro bit

  32. intosi

    Make sure you pronounce it right.

  33. intosi

    Remember: zimpy

  34. Kev

    I'm quite happy with pronouncing it zimpy :)

  35. intosi

    I thought you would be.

  36. fippo

    https://twitter.com/HCornflower/status/405440973565468672 -- guess what, xmpp pushing webrtc forward once again :-)

  37. Lance

    \o/

  38. Lloyd

    Go fippo!

  39. MattJ

    Go XMPP!

  40. fippo

    go Jingle!

  41. fippo

    i don't think that will be ready for todays council or board meeting though ;-)

  42. fippo

    er... tomorrow

  43. MattJ

    When will it be ready? And does it work with Prosody? :)

  44. fippo

    well, https://lambada.jitsi.net is currently powered by prosody

  45. fippo

    it's using MUC... but that's an implementation detail

  46. fippo

    i really need to work with emil on making CoLiBri ready for submission

  47. fippo

    it trumps muji

  48. MattJ

    and COIN?

  49. fippo

    and probably the hangouts stuff google never published as well

  50. fippo

    well... i still dread COIN

  51. MattJ

    :)

  52. fippo

    but it's not used

  53. fippo

    three of the four clients in that videochat are mostly standard strophe.jingle ones

  54. fippo

    there is a proprietary extension, a custom jingle action

  55. fippo

    where i am not sure how to best solve that in a jingleish way

  56. SouL

    Awesom!

  57. SouL

    e*

  58. dwd

    So I'm assuming you're set to demo this and have a proper spec by FOSDEM, right?

  59. dwd

    No pressure, or anything.

  60. fippo

    sure. colibri is a dumb one job protocol

  61. fippo

    easy to document

  62. fippo

    "hey bridge, get me a channel"

  63. dwd

    And the rest?

  64. fippo

    stock jingle

  65. fippo

    and working around chrome bugs

  66. fippo

    I had it working with lance's unmodified stanzaio client until recently

  67. dwd

    What's the "proprietary extension"?

  68. fippo

    an addsource jingle extension

  69. fippo

    which has ssma children (which will be standard as soon as the xmpp editor returns from the well-deserved vacation and the council votes)

  70. fippo

    but that's it

  71. dwd

    Oh, wait. So out of four clients, A B C and D, A says to the bridge "hey, dude, channel!" and then basically spoofs the bridge's transport params to B, C, and D?

  72. fippo

    A is called "focus"

  73. fippo

    but yeah, that's it

  74. dwd

    OK, nice. So B/C/D don't need any special sauce? They can just be naïve Jingle clients?

  75. fippo

    A also relays some more information from B to C and D, C to B and D and D to B and C

  76. fippo

    mostly.

  77. fippo

    they need a little bit of extra information in chrome right now

  78. fippo

    and the ability to demux multiple video streams on the same rtp session

  79. dwd

    Oh, you're muxing. Gotcha.

  80. fippo

    because chrome muxes now

  81. fippo

    at some point chrome is going to do different m-lines for that

  82. fippo

    at least that is what's called unified plan

  83. fippo

    I prefer the current plan (B)

  84. fippo

    but there is no roadmap for unified even

  85. fippo

    i'd note that with unified, we'd solve the proprietary stuff in a standard compliant way

  86. fippo

    because that makes it a content-add

  87. fippo

    but for now i'll go proprietary :-)

  88. fippo

    fast, evil corporate way

  89. Zash

    fippo: You have a muxer?

  90. fippo

    zash: https://jitsi.org/Projects/JitsiVideobridge

  91. Zash

    fippo: That wasn't a muxer last time I checked, just a focus point that relayed everything to everyone