XSF Communications Team - 2020-03-10


  1. emus

    https://github.com/xsf/xeps/pull/903

  2. pep.

    Yep. Let's refrain from commenting on it if it's not for the form though :P

  3. emus

    I dont get it?

  4. pep.

    We try to keep github issues free of standards discussions :)

  5. emus

    pep.: Ah okay, but it was so thankful 😍 No, is fine, I delete it

  6. pep.

    no don't

  7. pep.

    That level is fine :)

  8. pep.

    It's just that we don't want a real chat in there

  9. emus

    Ah, okay too late 😅

  10. pep.

    So we don't multiply discussion venues

  11. emus

    Now everyone at least got it in their email :) I clicked some emojis

  12. pep.

    hehe

  13. emus

    We got Internet connection again, I think I can continue work tonight

  14. pep.

    great :)

  15. pep.

    What happened?

  16. emus

    pep.: "Vodafone" happened^^

  17. pep.

    hah

  18. emus

    We dont know what was wrong I could access some sites, some not (I mean everyone in the network). We tried resets etc... now we got a new ....what ever that vodafone router thing is called^^

  19. emus

    We dont know what was wrong: I could access some sites, some not (I mean everyone in the network). We tried resets etc... now we got a new ....what ever that vodafone router thing is called^^

  20. emus

    https://blog.process-one.net/go-xmpp-v0-5-0/

  21. vanitasvitae

    https://blog.jabberhead.tk/2020/03/10/omemo-specification-sprint/

  22. emus

    i yeahi

  23. Martin

    vanitasvitae: > Huge thanks to them for having us! Don'rvyou mean hosting?

  24. vanitasvitae

    having us means basically the same

  25. vanitasvitae

    "Thanks for having me" is something like "Thanks for being here"

  26. emus

    Omg.... what exactly do I need to look for in the mailinglist? pep. ?

  27. pep.

    let me see

  28. pep.

    There are quite a few :/

  29. emus

    and, actually, thats March, is that right?

  30. emus

    I mean, I personally don't 100% get whats important for the newsletter, and how I workthrough it best?

  31. pep.

    The target of the XSF is developers (XMPP users, not XMPP client users), so it makes sense

  32. pep.

    (nor XMPP server users)

  33. pep.

    Ok so.. I have the following:

  34. emus

    Yes, I understand - but I don understand how to look for what xeps? 😅️

  35. emus

    As I said - I hate mailing lists xD

  36. emus

    and mail in general

  37. emus

    Not that I dont use it actively, but in general, I have my reasons xD

  38. emus

    sorry, I forgot you also send me the February link

  39. emus

    So, I just grep something like: https://mail.jabber.org/pipermail/standards/2020-February/037037.html

  40. emus

    Okay, now I think I got it

  41. emus

    pep. Im gonna collect it, then you can review

  42. pep.

    ProtoXEP: - https://mail.jabber.org/pipermail/standards/2020-February/037034.html : Simple JSON Messaging - https://mail.jabber.org/pipermail/standards/2020-February/037063.html : Extended Channel Search - https://mail.jabber.org/pipermail/standards/2020-February/037035.html : Trust Messages Active: - https://mail.jabber.org/pipermail/standards/2020-February/037032.html : XEP-0345 (Form of Membership Applications) Experimental: - https://mail.jabber.org/pipermail/standards/2020-February/037091.html : XEP-0434 (Trust Messages) Deferred: - https://mail.jabber.org/pipermail/standards/2020-February/036998.html : XEP-0386 (Bind 2.0) Last Call: - https://mail.jabber.org/pipermail/standards/2020-February/036997.html : XEP-0398 (User Avatar to vCard-Based Avatars Conversion) - https://mail.jabber.org/pipermail/standards/2020-February/037037.html : XEP-0402 (PEP Native Bookmarks) Draft: - https://mail.jabber.org/pipermail/standards/2020-February/036990.html : XEP-0363 (HTTP File Upload) Call for Experience: - https://mail.jabber.org/pipermail/standards/2020-February/037071.html : XEP-0066: Out of Band Data - https://mail.jabber.org/pipermail/standards/2020-February/036992.html : XEP-0368: SRV records for XMPP over TLS - https://mail.jabber.org/pipermail/standards/2020-February/036986.html : XEP-0198: Stream Management

  43. pep.

    That's what I have

  44. pep.

    There are "duplicates", some went through multiple stages in a month

  45. emus

    Puhh... I have to learn a lot I guesss

  46. emus

    pep. ProtoXEP = New ?

  47. pep.

    yes

  48. pep.

    "Proposed Extension" in the list

  49. pep.

    Ah wait no

  50. pep.

    hmmm

  51. pep.

    hah, that's confusing

  52. pep.

    "Proposed" is the state XEPs are in when they're in Last Call

  53. pep.

    But "Proposed Extension" in the list is used for ProtoXEPs :p

  54. pep.

    Read 0001 someday when you have time :)

  55. emus

    Okay, Im gonna do it - I think New suits, or?

  56. pep.

    New suits?

  57. emus

    The ProtoXEP suits the section 'New', agreed?

  58. pep.

    Yes

  59. emus

    I have a better suggestion: We create a new section called: === Miscellaneous ====

  60. emus

    becuase, what to do with: Call for Experience:

  61. emus

    Draft:

  62. emus

    Or.. coming back: ProtoXEP:

  63. pep.

    So what would it look like?

  64. emus

    wait+

  65. emus

    I create the draft

  66. pep.

    ok

  67. emus

    pep. I'm not satisfied with formating, but its readable