XSF Communications Team - 2020-05-07


  1. emus

    Release is out! Who can publish on twitter etc?

  2. peetah

    great ! thanks !

  3. peetah

    no yet on the website ?

  4. peetah

    not yet on the website ?

  5. wurstsalat

    emus: great! I see specification points have a slightly different formatting now, and I think it's better that way. I opened a PR against the may draft (again, specifications). I'll update that one to the new formatting as soon as I find the time

  6. emus

    wurstsalat: whats it exactly?

  7. wurstsalat

    emus: URLs are integrated, so XEP-xxxx becomes a link to the updated spec

  8. emus

    Ah ok. yes was peetahs sugggestion. right? or was also yours?

  9. wurstsalat

    not mine :)

  10. emus

    ok

  11. emus

    Also the website publish is outstanding

  12. emus

    sorry, pending

  13. peetah

    is DarkiJah a real user or a nick spammer ?

  14. emus

    In here?

  15. peetah

    yes

  16. emus

    ah, Im not sure, I saw him posting in other mucs, but dont know if that was spam

  17. Licaon_Kter

    emus: it's spam-mish...

  18. peetah

    its nickname is spammish for sure

  19. emus

    馃榿 bei.g spamish is the real spam

  20. peetah

    his/her nickname is spammish for sure

  21. emus

    I have no admin rights to kick. However he does not spam in here

  22. Licaon_Kter

    > mail01.tinyletterapp.com uses an invalid security certificate. The certificate is only valid for the following names: cloudfront.net, *.cloudfront.net Error code: SSL_ERROR_BAD_CERT_DOMAIN

  23. peetah

    here is my point of view: in this room I don't see the point to add a website to a nickname, moreove if it has a religious purpose

  24. emus

    intosi, ralphm, N每co, SouL: Do you know who can do something about it?

  25. emus

    Shall I ask infra team?

  26. emus

    peetah: yes, sire

  27. N每co

    About what

  28. emus

    sure

  29. emus

    N每co: the cert

  30. emus

    ^

  31. peetah

    I'm not saying something should be done, just that I'm not comfy with it and we should at least ask him/her to make it simpler

  32. emus

    Im not awaking the spammer 馃榿

  33. SouL

    emus: we can't do anything. It is tinyletter who has to fix it

  34. Licaon_Kter

    Great month. Thanks for everyone that helped. 馃憤

  35. emus

    > Great month. Thanks for everyone that helped. > 馃憤 馃憤

  36. emus

    > emus: we can't do anything. It is tinyletter who has to fix it Ah ok

  37. larma

    fwiw, the section on Dino is misleading because it sounds like those new features have been released, but there is no release with them yet. In contrast Gajim section makes very clear that the changes are for the next release...

  38. emus

    > fwiw, the section on Dino is misleading because it sounds like those new features have been released, but there is no release with them yet. In contrast Gajim section makes very clear that the changes are for the next release... Hi larma, sorry was my fault. From my inherently understanding, put it in as a progress information

  39. emus

    same goes for UWPX

  40. larma

    no big issue, just noticed so you know for next time 馃憤

  41. emus

    Won`t do it, if you don't like it, if thete is no release

  42. larma

    I think it's OK to mention that those features will be in the next release. Just don't want to set wrong expectations of them being available now (master isn't really for everyone to use)

  43. emus

    Ok, next time I will improve and also contact you before to clear formulation

  44. pep.

    > peetah> here is my point of view: in this room I don't see the point to add a website to a nickname, moreove if it has a religious purpose I agree. I asked them to change their nick and after some time of non-response I kick them out of my service

  45. pep.

    There's nothing in place at the XSF level to report this and that annoys me

  46. emus

    "after some time" = 5s "naahhh goodbye!!!" 馃槀馃槀馃槀

  47. emus

    pep.: good idea actua'ly

  48. peetah

    for those willing to proof read the french translation before publication https://linuxfr.org/redaction/news/collaboration-via-internet-7-may-2020 (registration required)

  49. emus

    cool

  50. pep.

    peetah, reading

  51. pep.

    > The XSF is renewing its sponsorship for 2020 Probably too late now but this seems badly said

  52. pep.

    The XSF is not sponsoring anybody

  53. pep.

    I'm not entirely sure I like the tone of this newsletter, but I didn't help with it so I can't say anything about it. I mean words like "cool / not cool" or "Bam", etc.

  54. emus

    馃 is that apart from Alex email what he wrote? Becuade I copied it from there more or less

  55. Licaon_Kter

    pep.: too hip for you old man :))?

  56. emus

    Its my tone... I wonder why we shouldnt be happy about the things happen

  57. pep.

    Licaon_Kter, yeah maybe :)

  58. Licaon_Kter

    emus: not enough smilies? Oh use stick.....sorry...bad word in xmpp world

  59. emus

    > emus: not enough smilies? Oh use stick.....sorry...bad word in xmpp world I dont need your unnecessary sarcasm here

  60. pep.

    emus, I don't mean to offend of course, I appreciate the effort / time spent first of all

  61. pep.

    peetah, 芦 geo-localisations 禄 ? 脟a s'accorde (pluriel) ? 脟a prend un accent aussi g茅o peut-锚tre ?

  62. emus

    Is fine, I can imagine that this is too much for one or the other. However, I hope its clear that this is a newsletter not written like a XEP or so

  63. peetah

    pep.: fixed

  64. pep.

    芦 Dans leur blog, ils expliquent 茅galement comment contribuer plus facilement via leur d茅p么t. 禄 脟a fait bizarre perso, traduit de 芦 they 禄 au singulier (?)

  65. pep.

    脟a existe pas vraiment en fran莽ais. Faudrait peut-锚tre tourner la phrase diff茅remment ou alors utiliser une 茅criture un peu nouvelle 芦 inclusive 禄

  66. peetah

    pep.: if you don't mind, let's do this in the trib茂oune next to the text ;)

  67. pep.

    Ah, another chat thing :p

  68. pep.

    peetah, I've done a first pass, seems good to me, thanks :)

  69. peetah

    thanks

  70. emus

    who has access to the social media accounts? That we can link there too?

  71. pep.

    hmm, jcbrand ^? N每co for sure

  72. jcbrand

    I have access to Twitter, but that's all

  73. jcbrand

    Link what where?

  74. emus

    jcbrand: I mean create a post, like we did for the previous ones. You can basically copy paste it I thinl

  75. jcbrand

    Can you give me something to copy paste?

  76. emus

    Collaboration over the Internet! Checkout the newsletter, with lots of software updates and specifications progress. https://xmpp.org/2020/05/newsletter/ #xmpp #jabber #decentralised #federated The picture can be take from from.the previous one: https://xmpp.org/2020/05/newsletter/

  77. jcbrand

    Ok, on it

  78. jcbrand

    What picture? I don't see it

  79. jcbrand

    found it

  80. emus

    jcbrand: sorry, this link https://twitter.com/xmpp/status/1231849365972684800

  81. emus

    ok

  82. jcbrand

    https://twitter.com/jcopkode/status/1258447703861796865

  83. jcbrand

    oh ahir

  84. jcbrand

    shit

  85. emus

    馃榿

  86. jcbrand

    Let's try again

  87. emus

    Its nice you advertise from your account aswell 馃槉

  88. N每co

    What

  89. jcbrand

    https://twitter.com/xmpp/status/1258448128841302017

  90. jcbrand

    Gotta run...

  91. emus

    nice

  92. emus

    馃憣

  93. emus

    jcbrand: Can you also tweet a reminder on our open draft? I will create the text and you can publish it (to the @XMPP 馃槈)?

  94. emus

    Next XMPP Newsletter is already open for link submission! New: We do the drafting on Github - please report all notable activities! https://github.com/xsf/xmpp.org/pull/706 [Newesletter image]

  95. emus

    You dont need to do it now, when you have time