XSF Discussion - 2019-04-29


  1. atomicbutter

    Subscribe to this youtube channel: https://www.youtube.com/channel/UCJMr4LzZvisWnfK1Ilk2RnQ?view_as=subscriber

  2. rion

    Hi guys. What do you think if I make a PR to jingle-s5b spec according to my remarks on wiki. It will also require advance its ns

  3. rion

    Basically I'm going to introduce candidate-complete event with meaning no more local candidates (trickles) left.

  4. rion

    This will allow significally simplify negotiation with trickles. And the advice to put as many as possible candidates to session-initiate won't be that relevant anymore

  5. flow

    rion, trickles?

  6. rion

    The candidates sent with transport-info

  7. rion

    Additional candidates

  8. flow

    rion, Is that term somewhere defined? I just greped the XEPs repo for it

  9. rion

    Basically it's related to ICE

  10. flow

    rion, I would suggest posting at least a strawman of your proposed changes to the standards@ mailing list, then wait for feedback and eventually create a PR

  11. jonas’

    given that this is jingle, I don’t expect any feedback on the list :(

  12. flow

    I'd also CC the authors of the xep (I suppose we are talking about xep260?), but don't expect much feedback

  13. flow

    what jonas’ said, but at leat it is archived and documented somewhere…

  14. flow

    I also would not be surprised if a namespace bump experiences some resistance. But my impression of is jingle possibly deserves an overhaul…

  15. pep.

    There's a jingle feature arriving on dino, I'm sure they would have a look. Also there's a few clients implementing it.

  16. rion

    That's why I want to change it. I'm implementing it in Psi and found many unclear parts. But this current state of jingle-s5b forced me to implement some overcomplecated logic. I don't like it at all.

  17. flow

    ideally we would be able to bundle all changes, and not namespace bump on every single one. Smack also has some ongoing jingle work, but I don't expect it to be finished before the end of the year

  18. jonas’

    if only we had a proper staging area for updates to Draft XEPs

  19. flow

    and a staging namespace

  20. jonas’

    possibly that, too

  21. flow

    urn:xmpp:jingle:5-(next|dev|staging|…)

  22. pep.

    Semver-ns

  23. pep.

    urn:xmpp:jingle:5.1

  24. rion

    +1 for semver

  25. jonas’

    they are already semver

  26. jonas’

    if the changes are non-breaking, you don’t need to bump the namespace

  27. jonas’

    so you don’t need the minor version number in the NS

  28. flow

    yep, I don't also don't see a reason to use something like semver for xmpp namespaces

  29. pep.

    jonas’: sure, I could bump major at every single change and I would also be semver compliant

  30. pep.

    But that's not really the idea

  31. jonas’

    pep., that’s not at all what I was saying

  32. rion

    Ok I'll post on ml tomorrow

  33. pep.

    jonas’: I was saying there's different readings of that spec (as there is for every spec)

  34. rion

    Btw, I can split my proposal in two parts. First is not breaking. It just says to not send candidate-error/used until all local and remote candidates are acknowledged. And this also suppose if candidate-error/used was send by remote and we send a new candidate to remote afterwards, the remote state machine has to invalidated. It's not a requirement though. Another part is the candidate-complete event

  35. rion

    Decided to send my thoughts now. It's on ml =)

  36. yvo

    pdurbin, have I conviced you? Become a member :). If you are a member on the XSF conf you have dinner for free :D. Plus Cap! :-o

  37. Zash

    <blink>FREE DINNER</blink>

  38. rion

    Now I want to be a member too!

  39. Ge0rG

    It's only free if you live in Brussels.

  40. rion

    😭

  41. pdurbin

    Heh.

  42. Ge0rG

    That said, https://wiki.xmpp.org/web/Membership_Applications_Q2_2019

  43. Ge0rG

    > Applications will be accepted until end of business May 12th, 2019

  44. yvo

    XD

  45. Seve

    > It's only free if you live in Brussels. Not true >:(

  46. Zash

    s/Brussels/that tiny village where the restaurant is/ ? :)

  47. yvo

    Zash yes <blink>TINY VILLAGE</blin>

  48. yvo

    Zash yes <blink>TINY VILLAGE</blink>

  49. pdurbin

    Before I join, I'm trying to figure out if I can have a user experience I'm happy with. The big thing is history. Slack excels at this. I used Conversations over the weekend on Android and fired up a second client today, Adium on a Mac. From Adium I don't have access to my one-to-one history that happened on Conversations like I would on Slack. Is there a solution for this? Is this the fault of my XMPP provider (FSF)? Can they enable history or something?

  50. yvo

    :D pdurbin

  51. yvo

    What you are asking for is called MAM.

  52. Zash

    pdurbin: I think the problem is that Adium is outdated.

  53. j.r

    But MAM is useless with later joined OMEMO devices

  54. yvo

    With Mac you are unfortunately in a not so nice situation. You should ask for another client.

  55. yvo

    j.r I think he asks for MAM in this MUC here thus no omemo keys ...

  56. yvo

    Zash, what was again the best client under MacOS? I forgot it.

  57. Zash

    I don't run MacOS, so I'm no authority on this.

  58. Zash

    Monal is more actively developed at least, so give that a shot?

  59. eevvoor

    Hi

  60. Zash

    Hey

  61. Zash

    https://xmpp.org/software/clients.html had more MacOS options listed than I expected

  62. pdurbin

    Sure, I can try Monal tomorrow. Thanks!

  63. atomicbutter

    Watch this really cool video, also subscribe to the channel! https://www.youtube.com/watch?v=sVzBhGE3w40

  64. atomicbutter

    Watch this really cool video, also subscribe to the channel! https://www.youtube.com/watch?v=sVzBhGE3w40