XSF Communications Team - 2019-11-08


  1. Nÿco

    the newsletter is sent, check your inbox! yoohoooo :)

  2. Nÿco

    for the blog post, the GitHub PR is waiting for a merge and deploy meanwhile we can copywrite the tweet

  3. Nÿco

    How about this? " The XMPP Newsletter is out! This Friday 08 Nov 2019 Sprints, IoT, and early Twitter Articles, tutorials, events, plus all the software and specifications updates! #IETF #XMPP #Jabber #OpenStandards #OpenSource "

  4. Nÿco

    link collection open for December: https://wiki.xmpp.org/web/XMPP_Newsletter_December_2019

  5. Martin

    > This Friday 08 Nov 2019 I would remove this and just add a 'now' to the prior sentence. The date is in your tweets timestamp anyway.

  6. emus

    > I would remove this and just add a 'now' to the prior sentence. The date is in your tweets timestamp anyway. Point

  7. emus

    Nÿco: Have you created a new sheet for the translations

  8. Nÿco

    >> This Friday 08 Nov 2019 > I would remove this and just add a 'now' to the prior sentence. The date is in your tweets timestamp anyway. no, on social media posts live several days (a few like 3 ot 5 on Twitter, more on LinkedIn like 7 to 10) so relative dates just don't work, we have to deal with absolutes (not only Siths)

  9. Nÿco

    > Nÿco: Have you created a new sheet for the translations nope, not yet I understand you are suggesting I do it, correct? well, I hesitate: * on one hand that may encourage people to translate as the working document is then already created * on the other hand, leaving some space for own tools gives more freedom and flexibility so I created those pages for German and Spanish? the French translations usually are worked on an Etherpad

  10. pep.

    https://github.com/xsf/xmpp.org/pull/632/files#diff-614cbf5566dea54475d4909816a7c7e2R54 Nÿco, probably not significant if it doesn't appear in the rendered version, but there's an extra space after the "*"

  11. pep.

    For next newsletters, I think we should avoid Last Calls, maybe. They're time-sensitive and it's always a mismatch

  12. Nÿco

    wow, good catch! thx :)

  13. Nÿco

    yeah, Last Calls, still good to mention I mean the Last Calls have been receive by the involved people in the Standards ML but here, we inform the outside of that circle, so why remove the Last Calls? this is a Must-Have information that a spec has passed that milestone

  14. Nÿco

    so indeed that needs some sort of different presentation, I still don't know how

  15. emus

    nyco, okay, then I translate and drop it once ready

  16. Nÿco

    what's best

  17. Nÿco

    I am working on... https://mensuel.framapad.org/p/xmpp-newsletter-francais-2019-10-01-hpuzcnu7mq?lang=fr

  18. pep.

    ok I have 20mn

  19. pep.

    Let's do this

  20. pep.

    where's the first link? for october

  21. Nÿco

    hehehe

  22. Nÿco

    the what?

  23. pep.

    Is it only this month?

  24. pep.

    We missed the previous one right?

  25. Nÿco

    what month?

  26. Nÿco

    I am working on: https://mensuel.framapad.org/p/xmpp-newsletter-francais-2019-10-01-hpuzcnu7mq?lang=fr

  27. Nÿco

    please check and read the header

  28. pep.

    last newsletter on jabberfr is september 3rd

  29. Nÿco

    latest

  30. Nÿco

    https://mensuel.framapad.org/p/xmpp-newsletter-francais-2019-10-01-hpuzcnu7mq?lang=fr October still in progress here

  31. pep.

    ok ok

  32. Nÿco

    argh, sorry, I gotta now, I'll be back

  33. pep.

    > Multiple vulnerabilities have been found in Dino, please update as soon as possible if you are a Dino user.

  34. pep.

    Can we add a date here. I think I've seen this last month already

  35. pep.

    People are gonna think dino is full of security vulns

  36. pep.

    Ah wait, that's october..

  37. Nÿco

    Covering September, yes we are late, we missed one

  38. pep.

    > Converse users may find useful the new plugin to verify HTTP Requests via XMPP from Agayon This is badly said

  39. pep.

    I have a hard time translating

  40. Nÿco

    But it is published

  41. Nÿco

    I'll do it

  42. pep.

    Sure

  43. Nÿco

    This has been reviewed by real native English speaker

  44. Nÿco

    s

  45. pep.

    Yeah maybe the sentence is correct english

  46. pep.

    But it doesn't reflect what 0070 does

  47. Martin

    Take bullet points about the information and build the french sentence from scratch. This is how I translate stuff as trying to transform a sentence to another language often leads to awkward grammar.

  48. pep.

    Martin, yeah. I don't have much time right now though

  49. emus

    But I can start translating from the mainversion?

  50. Nÿco

    > But I can start translating from the mainversion? sure you can, why not? it's just that the French translations are late

  51. Nÿco

    resuming the French translation, sorry

  52. pep.

    I'll be available with a laptop again tonight

  53. emus

    Nÿco: I think I can make a draft aswell by tonight

  54. Nÿco

    don't worry pep. I'll publish it on LinuxFr.org

  55. pep.

    K

  56. Nÿco

    I've done the copy-paste here: I hope there will be some reviews

  57. Nÿco

    https://linuxfr.org/redaction/news/lettre-d-information-xmpp-01-octobre-2019-fosdem-2020-modernisation-de-xmpp-reseaux-de-pairs

  58. Nÿco

    images added

  59. Nÿco

    boom: https://xmpp.org/2019/11/newsletter-08-november/

  60. Nÿco

    and boom: https://twitter.com/xmpp/status/1192836120725409794 please retweet

  61. Nÿco

    https://upload.movim.eu/files/1ab8cd5d50a081e2fdf8ce43dca3047f8bd49889/toDryBysxbDSAl1XqDdaB9ThLvrOkeOOEZ0DReJe/Capture_d_e_cran_2019-11-08_a__17.12.05.png

  62. Nÿco

    we'll check again on Monday

  63. emus

    guys, is that intended?

  64. emus

    https://xmpp-share.mailbox.org/upload/mailbox.org/cf9b0bfb1642efa7ddd6e519af9dbaa1ccd6e42c/enbePSI6SwViBpu3Cjh7cdOiNAfYC7TAavkqoLxI/IMG_20191108_184121.jpg

  65. emus

    Nÿco, pep.:

  66. pep.

    Probably not?

  67. pep.

    Dunno

  68. pep.

    Still not in front of a computer

  69. ldkjgoiwe

    That's the alt description of the picture that should be there. The image displays fine for me, though.

  70. emus

    Do we have a holistic tracking about User app whose got updated? Guess there is likely more 🤔

  71. emus

    hnm weird. my uMatrix seem to block obly this

  72. emus

    hmm, no still only text. do you have a screenshot for me?

  73. emus

    ldkjgoiwe:

  74. ldkjgoiwe

    uhm, yeah https://imgur.com/a/Mtv7lEn

  75. Nÿco

    Where is that image not displaying?

  76. emus

    Nÿco: on my firefox

  77. emus

    Nÿco: what do you guys mean by: early Twitter

  78. emus

    ldkjgoiwe: is the picture clickable?

  79. ldkjgoiwe

    read the page source 😛 no it's not

  80. ldkjgoiwe

    I took some time writing down remarks and suggestions regarding the newsletter tweet. There are many opinions in there, so I didn't write "IMHO" every time: 1. The picture. I am aware of the statistics saying that you get more engagement if you have an image compared to if you don't. However, I also strongly feel that an image, if used, should have some "quality". And the images used for the newsletter tweets don't fullfill that property. Please don't take that critique too negatively: We are mostly software engineers and computer-people, not designers. However, IMHO not posting an image is better than posting a bad one. Especially since twitter displays a box with info about the link below the tweet if no image was supplied - and the link is the most important thing about the tweet, so having that box would be fine. 2. As was already pointed out in #xsf, the link to the article is missing. I assume this is because the newsletter was sent before the blog post was merged? Again, the link is the most important thing about that tweet because that's where we want the people to click and read. The twitter followers have no use in knowing that other people got an email - they want to get the content. I understand that you want people to subscribe, but it should also be fine for people to follow @xmpp on twitter and get their news from there, if they wish so. 3. Full sentences would be more appealing than lists without context. 4. Perhaps write something in front of the link like "Read more here:", "Read the newsletter here:", to highlight the link and make the action item clear. 5. There is no need for two newlines between every sentence In total, my suggestion would be something like: "The November Newsletter is out with news from the XMPP ecosystem! This time it contains info about a recent sprint, early Twitter days and as always recent articles, software releases and much more! Read it here: https://example.com" [no image]

  81. ldkjgoiwe

    @ Nÿco SouL jcbrand

  82. Nÿco

    emus Firefox, but blog post or inbox email newsletter ?

  83. Nÿco

    1. I know, the symbolic is not the best, and quality (resolution) is not high I'd be happy to change it, what would you suggest?

  84. Nÿco

    2. Oh sh*t, I forgot the link... :( Shame...

  85. Nÿco

    3. Not always, depends what you want to convey, here it is al list of things inbthe content Again, happy to change for better, if suggestions are made

  86. Nÿco

    4. No need for a "read" on Twitter, it's short and you save characters Plus people know how to click a link if they want (and if there is one... :'( )

  87. Nÿco

    5. It is a question of taste

  88. Nÿco

    Oh and 1. Qualities of displays vary a lot

  89. emus

    I agree with most arguments, but I think there should be some pictures. And it should be readble in a quick manner I think

  90. Nÿco

    The final suggestion is awesome, I'll post it next week, but with an image

  91. emus

    Nÿco: what do you guys exactly mean by: early Twitter

  92. Nÿco

    I apologise for my lack of presence in the past weeks, health issues, usually I propose the tweets for review or co-construction earlier...

  93. emus

    Further more: there is a 404 from Part 2 Nÿco: on my firefox https://www.erlang-solutions.com/blog/xmpp-protocol-build-an-ios-instant-messaging-app-part-2.html

  94. Nÿco

    I'll improve that for the next issue

  95. ldkjgoiwe

    > 1. I know, the symbolic is not the best, and quality (resolution) is not high I'd be happy to change it, what would you suggest? > The final suggestion is awesome, I'll post it next week, but with an image Well my suggestion would be: Either put together an image that is actually visually appealing, or leave it out completely.

  96. Nÿco

    No, an image is better than nothing, unless it is aweful, and in our case it is not

  97. ldkjgoiwe

    > The final suggestion is awesome, I'll post it next week, but with an image Generally I'm not a fan of posting the same thing multiple times. This has unfortunately been done with "Newsletter Subscription Reminders" in the past. I guess in this specific case one could argue that reposting is ok, but only because the original post did not contain the link.

  98. ldkjgoiwe

    > unless it is aweful, and in our case it is not I respectfully disagree 😀

  99. Nÿco

    Remember: Done is better than perfect Too late is better than nothing

  100. Nÿco

    Fan or not, it is a good practice

  101. Nÿco

    And doing is better than arguing, qnd facts better than opinions, and experience better than guessing, respectfully

  102. ldkjgoiwe

    You seem to view my statement as an attack on you. This was not my intention. As I already said: Please do not take critique of the picture negatively: We are software developers, not designers.

  103. emus

    ldkjgoiwe: I mean, are the pictures really awful?

  104. emus

    Nÿco: In ready to put it to the wiki

  105. emus

    Im

  106. Nÿco

    I said I will improve next issue, than means I habe heard you, and your comments make sense Thank you very much for this, I truly appreciate

  107. Nÿco

    Each time I have such feedback, it helps me a lot, so again thanks my dear friends

  108. ldkjgoiwe

    My sarcasm radar is confused. So I'll just assume your statements to be sarcasm-free 🙂

  109. Nÿco

    I don't master the Great Art of sarcasm It is too risky

  110. Nÿco

    It's true, I thank you for your very structured feedback

  111. emus

    Happy editing: https://wiki.xmpp.org/web/German_Newsletter_translation_of_November_2019 Martin, vanitasvitae debacle and everyone else speaks neu-deutsch

  112. emus

    whi*

  113. emus

    who

  114. emus

    > My sarcasm radar is confused. So I'll just assume your statements to be sarcasm-free 🙂 I think he will consider your suggestions fron the next version

  115. emus

    Ob sunday I will forward this to Jabber.de though

  116. emus

    On*

  117. Nÿco

    What is neu-deutsch? :)

  118. Nÿco

    New German?

  119. Martin

    Will try to find time to have a look later or tomorrow.

  120. emus

    > What is neu-deutsch? :) > New German? direct translation - yes.... but with sarcasm no^^ means something like the "new German" has some degration involved and lots of anglizims (?) make the people creative nowadays^^

  121. DebXWoody

    😁

  122. ldkjgoiwe

    Nÿco, I put some alternative images together. You can use them if you want. https://imgur.com/a/MwQ77Wd

  123. emus

    ldkjgoiwe: Please upload them to the wiki

  124. pep.

    Yep that looks cool

  125. Nÿco

    > Nÿco, I put some alternative images together. You can use them if you want. https://imgur.com/a/MwQ77Wd wow, great! thanks a lot! :)