XSF Communications Team - 2020-02-03


  1. N每co

    starting the copywriting of the newsletter, means link collection is closed

  2. Licaon_Kter

    馃憤

  3. Licaon_Kter

    You'll include Snikket too right?

  4. N每co

    nope, it's on 1st of Feb that has been announced :)

  5. Licaon_Kter

    Dammmit :))

  6. Martin

    Will you clarify that the 0.8.0 release announcement in the last newsletter was wrong?

  7. N每co

    of what?

  8. Martin

    Profanity

  9. Martin

    Sorry. 馃槂

  10. N每co

    why not

  11. N每co

    can you please prepare me a short one-liner?

  12. N每co

    we could add a "sorry I f**ked up" section :)

  13. Martin

    In the last newsletter we announced the release of profanity 0.8.0 due to a misunderstanding. Please be aware that profanity 0.8.0 is not yet released. Buuut, the 0.8.0 will come these days so maybe it will be released by the time people read the newsletter. So maybe add some date of the newsletter deadline?

  14. Martin

    > we could add a "sorry I f**ked up" section :) 馃槀

  15. Licaon_Kter

    > nope, it's on ???st of Feb that has been announced :) Martin: ^^^^

  16. Martin

    What?

  17. Licaon_Kter

    Martin: if it's announced in Feb doesn't matter...

  18. Licaon_Kter

    ..for January's newsletter

  19. Martin

    I know, but saying it is not yet released but maybe it got released yesterday seems also weird. So say is not yet released by the date of. ..

  20. N每co

    > So maybe add some date of the newsletter deadline? the planning section is always there: https://wiki.xmpp.org/web/XMPP_Newsletter#Planning

  21. N每co

    > In the last newsletter we announced the release of profanity 0.8.0 due to a misunderstanding. Please be aware that profanity 0.8.0 is not yet released. good, thx!

  22. Licaon_Kter

    Martin: i know

  23. Martin

    Released: https://github.com/profanity-im/profanity/releases/tag/0.8.0

  24. N每co

    hehehe

  25. N每co

    well done

  26. Martin

    I'm only a user 馃槂

  27. Licaon_Kter

    Martin: :))

  28. Ge0rG

    I've released yaxim 0.9.9 in January, but I honestly wasn't able to add it to the wiki yet

  29. Licaon_Kter

    No F-Droid version? Meh no lauch :))

  30. Licaon_Kter

    No F-Droid version? Meh no launch :))

  31. N每co

    Ge0rG : it's added! (and tested)

  32. Ge0rG

    N每co: aweomse, thanks. Will it land in the January newsletter? I'm so excited! :D

  33. N每co

    yes sir

  34. N每co

    great update, btw

  35. pep.

    N每co, I'm compiling minutes for the Summit. When do you think the newsletter gets out?

  36. N每co

    oh wow!

  37. pep.

    I don't think I'll make it for today though, there are quite a few pieces missing in the minutes and I'd like to poke people who lead some topics again

  38. N每co

    ok, got it

  39. N每co

    so, I drafted this: ===== Events As usual in this period of the year, the community of protocol makers united in the XMPP Summit. Two days of sharing and building the future of XMPP. This year has been productive, we covered various subjects such as: XMPP Shortage Audit Easy Passwordless Onboarding and Account Management Account Rich Presence in PEP MLS End-to-End Encryption Key Management Palaver IM Client Why Push Notifications are not good enough? MIX when? IM-NG commTeam ("Lightning talk") Inbox / Unread / Bind2 XMPP as mandatory standard? (Lightning talk) Stickers XHTML-IM2 / Rich markup We will probably cover all these in more depth next month. =====

  40. N每co

    in https://wiki.xmpp.org/web/XMPP_Newsletter_February_2020#Events

  41. pep.

    Maybe also link to vanitasvitae's threads on mastodon(?)

  42. N每co

    this will leave time for people to sync and collab on an article

  43. N每co

    oh yeah, of course, sorry, forgot

  44. pep.

    Okay

  45. N每co

    found: https://fosstodon.org/@vanitasvitae/103571845414141817

  46. pep.

    There's one per day iirc

  47. N每co

    so, I go with my draft? I'd love to publish the newsletter tomorrow, as I announced/proposed

  48. N每co

    ok, I'll look for the second

  49. pep.

    yeah go with it. I'll try to hurry a bit (and push the concerned people), but if I don't make it it's fine :p

  50. pep.

    Ah apparently the second day is just in the same thread

  51. pep.

    https://fosstodon.org/@vanitasvitae/103577121536634734

  52. pep.

    So that link above is fine

  53. N每co

    thx

  54. N每co

    merci :)

  55. vanitasvitae

    pep.: I created one separate post as entry point for day 2 :P

  56. pep.

    ah ok

  57. pep.

    Can you link to both?

  58. N每co

    yeah, threads are still not crazy, bth on Mastodon and Twitter

  59. N每co

    https://wiki.xmpp.org/web/XMPP_Newsletter_February_2020#Events updated

  60. pep.

    https://upload.bouah.net/upload/9-alObjSJAkgMdDF/R-XEUGHJTb6uBMfnLNL5Yg.jpg

  61. pep.

    Can somebody help me decrypt the Key/Keys .. topic?

  62. Licaon_Kter

    pep.: the pad content isn't enough?

  63. pep.

    "Signing".

  64. pep.

    I had it on the previous picture (day1), but I lost context as one of the notes was removed :x

  65. vanitasvitae

    Basically its "key management is hard. Cross signing is stupid, key sharing is possible, master key is key." (Pun intended)

  66. N每co

    please review: https://github.com/xsf/xmpp.org/pull/673

  67. N每co

    > Can somebody help me decrypt the Key/Keys .. topic? on what item do you need help? I can try on the 2nd day items (I was missing on the first day)

  68. N每co

    "Ne pas retirer SVP" means "do not remove, please" :)

  69. N每co

    you're welcome :)

  70. Ge0rG

    N每co: reviewed on github

  71. N每co

    Ge0rG merci ! :)

  72. Ge0rG

    N每co: sorry for the brevity, but I'm veeeery short on time.

  73. N每co

    no need to be sorry, that helps a lot

  74. N每co

    https://wiki.xmpp.org/web/XMPP_Newsletter#Planning the dates I propose for next issue of the newsletter

  75. N每co

    metrics posted: https://wiki.xmpp.org/web/XMPP_Newsletter#Metrics.2C_statistics.2C_analytics