XSF Discussion - 2020-08-04

  1. jonas’

    https://googleprojectzero.blogspot.com/2020/08/exploiting-android-messengers-part-1.html

  2. MattJ

    > "This series highlights what can go wrong when applications don't apply WebRTC patches"

  3. Ge0rG

    business as usual.

  4. MattJ

    I imagine this is bad news for F-droid folk

  5. jonas’

    is it?

  6. MattJ

    afaik their build system is stuck on an old version of the WebRTC lib

  7. jonas’

    yikes

  8. MattJ

    There has been work underway to upgrade it recently, but I'm not aware that it's done yet

  9. jonas’

    Ge0rG, I seem to recall that you complain about the non-visibility of supersededby

  10. jonas’

    on deprecated XEPs, we mention superseded in the header: https://xmpp.org/extensions/xep-0048.html

  11. jonas’

    is that better?

  12. jonas’

    (or "good enough" at least)

  13. Ge0rG

    jonas’: is that new?

  14. jonas’

    no

  15. jonas’

    but it only affects Deprecated and stuff

  16. Ge0rG

    then I just never read to the end of the red colored wall of text

  17. jonas’

    yeah

  18. jonas’

    I thought about reformatting it a little

  19. jonas’

    but I’m running out of time today

  20. Ge0rG

    jonas’: what about: "Status: Deprecated by [XEP-0402](https://xmpp.org/extensions/xep-0402.html)"

  21. jonas’

    can be done, needs more code

  22. jonas’

    but indeed, linking the XEP would be very valuable

  23. Ge0rG

    a link in there would make it much more visible

  24. jonas’

    I need to put the lasagna into the oven, then I’ll see what I can do :)

  25. Ge0rG

    your priorities are right!

  26. emus

    Due to vacation time we lag a bit of reviews for the Newsletter. If there are any volunteers that would be a great help and also ensure quality. If one is interested please refer to: https://github.com/xsf/xmpp.org/pull/730/files Release is planned for the 6th, so about 48 hrs left.

  27. Ge0rG

    emus: the title "Article" should be "Articles". > support for Proxy Protocol which safely transport connection information This is in Mongoose and doesn't read right Tigase: > This version also improves management of multiple domains in virtual hosts and enable by default Should be "enables" The whatsxmpp MUC could be linked to

  28. emus

    Ge0rG: Thanks for reviewing! so far the muc links dont work to my understand nor get rendered (right?)

  29. Ge0rG

    emus: technically, you should be able to make an xmpp:?join link, or use something like http://join.jabber.network/#whatsxmpp@conf.theta.eu.org?join

  30. eta

    it was one!!

  31. eta

    at least in my comment I tried to make it one

  32. emus

    the website links are a good idea

  33. emus

    sorry eta, maybe I was a bit radical

  34. emus

    will change

  35. emus

    do we have something for XSF 😅️

  36. eta

    Ge0rG, also surely you leave off the #

  37. eta

    emus, to be fair to you I think github stripped it in my comment

  38. emus

    Will try again 🥊️🥋️

  39. emus

    [whatsxmpp@conf.theta.eu.org](xmpp:whatsxmpp@conf.theta.eu.org?join)

  40. emus

    that sthe situation

  41. emus

    the website is not HTTPS enforcing 🤨️

  42. Ge0rG

    eta: the # is required in that implementation

  43. emus

    yep

  44. eta

    Ge0rG, oh I missed that that was an HTTP link, oops

  45. emus

    https://github.com/xsf/xmpp.org/pull/730/commits/5ceffb1b20e276d0f83f492b6196e260d479bd96

  46. emus

    guys --> CommTeam Muc I suggest now - thanks for your support so far!

  47. vanitasvitae

    nice

  48. emus

    But the website should enforce HTTPS even if someone types HTTP only