XSF Communications Team - 2023-02-28


  1. nicola

    @wurstsalat I submitted a modification on GH

  2. wurstsalat

    nicola: where exaclty? I can't find it

  3. nicola

    > nicola: where exaclty? I can't find it Here: https://github.com/xsf/xmpp.org/pull/1253/files

  4. nicola

    Or here: https://github.com/xsf/xmpp.org/pull/1253

  5. wurstsalat

    not sure if I can't see it or if I don't understand you :) both links point to _merged_ files, and I don't see any comments. if these translations are from you, thank you for that!

  6. emus

    nicola: maybe just post it here?

  7. nicola

    > not sure if I can't see it or if I don't understand you 😊 both links point to _merged_ files, and I don't see any comments. if these translations are from you, thank you for that! My intervention was to change **line 27** with the following: **translation: "Questo articolo Γ¨ stato tradotto da volontari. Pur facendo del loro meglio, la traduzione potrebbe non essere accurata.”**

  8. emus

    thanks

  9. nicola

    > thanks U R welcome

  10. Licaon_Kter

    Re: pr, how come xep-0474 is both 'new' and 'updated' ? :)

  11. wurstsalat

    Licaon_Kter: that section hasn't been updated yet. I tend to wait until the end of the month, so thanks, good reminder :)

  12. Licaon_Kter

    πŸ‘

  13. nicola

    @emus here is my article on the DMA Workshop https://notes.nicfab.eu/en/posts/dmaworkshop/ If you have any comments, please let me know.

  14. emus

    Many thanks!

  15. nicola

    > Many thanks! U R welcome

  16. gooya

    nicola: Really interesting article thanks for writing it!

  17. Licaon_Kter

    nicola: 'e Jan` 'e Stephan' :)

  18. nicola

    The article is also available on my Gemini capsule here: gemini://notes.nicfab.eu/en/gemlogen/2023/2023-02-28-digitalmarketsact-workshop_en.gmi

  19. MSavoritias (fae,ve)

    oh nice

  20. MSavoritias (fae,ve)

    thanks πŸ˜€

  21. nicola

    > nicola: 'e Jan` 'e Stephan' 😊 Thank you @Licaon_Kter I corrected

  22. nicola

    I corrected also the title …

  23. emus

    nicola: --> newsletter

  24. emus

    neox: do you want to support the newsletter preparations outside of github this time? (other volunteers feel free)

  25. Licaon_Kter

    nicola: e Markus :)

  26. pep.

    Is it possible to talk about JoinJabber in the next newsletter maybe? Like promoting support channels?

  27. pep.

    We've added them in January but we forgot to put anything in the newsletter I think

  28. emus

    certainly, but maybe lets advertise the entire page of chats right away, too

  29. pep.

    Ah you mean the one on xmpp.org?

  30. pep.

    It's not referencing servers@joinjabber.org I think

  31. pep.

    https://joinjabber.org/about/community/ or this one?

  32. nicola

    > nicola: e Markus 😊 Omg! πŸ€¦β€β™‚οΈ Thank you @Licaon_Kter I corrected

  33. emus

    https://xmpp.org/community/chat/

  34. pep.

    I think I'd like to change the wording slightly. Specifically the "our" (support chat)

  35. pep.

    This isn't the XSF

  36. pep.

    Not entirely sure how to phrase it, but not this

  37. emus

    Well, tbh I wonder why we not just started again advertising the existing jUser chat instead of creating a new one

  38. emus

    just remove the "our" I would say

  39. pep.

    It's not a new one it's another one. They're not all the same. Policies matter

  40. emus

    yeah, fragmentation fun... has there been a discussion to get a policy for juser if thats so important? We can advertise it under announcement, but then page and chats too please πŸ™

  41. MSavoritias (fae,ve)

    emus the reason was that JoinJabber could get the moderation burden. Plus it was already setup with a site and outreach that people will see. Instead of xmpp.org which nobody finds by themselves

  42. emus

    Ok I see, but not sure if I understand. (In general I will not put much efforts in fragmenting or side paths when it comes to communication topics)

  43. MSavoritias (fae,ve)

    its simple. right now its written like the chat is from the xsf

  44. MSavoritias (fae,ve)

    (which is not)

  45. MSavoritias (fae,ve)

    its provided by the joinjabber collective

  46. MSavoritias (fae,ve)

    The "our" specifically that pep. mentioned.

  47. emus

    And why it cannot be done in the juser? thats discussion seem to pass by me

  48. emus

    MSavoritias (fae,ve): yes, I understand that

  49. emus

    and is correct of course

  50. MSavoritias (fae,ve)

    you mean why it was decided to have this room? Because it was active and it put less moderation burden on xsf as stated.

  51. MSavoritias (fae,ve)

    Plus people can find it from the joinjabber site

  52. pep.

    Specifically on jabber.org, but I guess folks there were happy leaving it away? Dunno

  53. MSavoritias (fae,ve)

    which makes more sense because no person will find xmpp.org

  54. emus

    MSavoritias (fae,ve): then why not change that? why they dont find it?

  55. pep.

    Whatever. If the XSF wants to advertize the juser room instead, do that. I personally won't fight it

  56. pep.

    In any case, we have a support room at joinjabber

  57. emus

    Im just confused again how things went rather as stated, we can advertise it, but should use the chance to advertise the other stuff too

  58. MattJ

    What juser room?

  59. emus

    https://xmpp.org/community/chat/

  60. MattJ

    There is no juser room on that page

  61. pep.

    MattJ, I assume emus is talking about the one room on jabber.org?

  62. pep.

    That existed, or maybe still exists, I don't know

  63. MattJ

    or confusing it with the juser mailing list

  64. MSavoritias (fae,ve)

    does that exist still?

  65. MSavoritias (fae,ve)

    I cant find it

  66. MattJ

    xmpp:jabber@conference.jabber.org?join exists

  67. emus

    yeah my bad

  68. MattJ

    It used to be the "user" equivalent to jdev

  69. MattJ

    There was never a juser chat

  70. MattJ

    But jabber@ these days is mostly about jabber.org specifically

  71. MattJ

    We could make it into a generic user support thing again, but I don't see why that's better than pointing to a joinjabber.org chat instead (which is already further in that direction)

  72. emus

    MattJ: then maybe this or will it be deprecated?

  73. emus

    I just bascially think: if we have xsf chat jdev chat editor chat counil chat at xsf then why not a user one

  74. emus

    or support

  75. emus

    ok, but we have that as a muc too

  76. pep.

    I'm going to make this point just because it's fun, not because I think it's a valid one: you're the one talking about fragmentation and you want to create yet another room? :p

  77. emus

    ok I see. but my point was ^

  78. MattJ

    For most of its history, jdev was on conference.jabber.org

  79. emus

    I need to go offlne pep.: feel free as said to add to the pad

  80. MattJ

    It was barely an "XSF" thing

  81. MattJ

    It was just a thing

  82. emus

    pep.: Yes, its right. but you need to step outside: My argumentation as always is: central communication in a decentral network

  83. pep.

    I'm not sure I understand, but from what I understand I think I disagree

  84. MSavoritias (fae,ve)

    the point was to change the support thing to something like: "Join the support chat provided by the JoinJabber community" or something

  85. pep.

    I'll PR it

  86. MattJ

    I neither agree nor disagree... I think some centralization is okay, and helpful. I don't think that can be used as an argument to centralize everything, which would be harmful.

  87. MattJ

    I am absolutely okay with our site pointing people in need of assistance to places where they can get that assistance

  88. nicola

    @emus I don’t know who is elaborating on the newsletter, but if you think it useful, you can add my other article entitled β€œDigital Service Act: EU Commission Questions and Answers on identification and counting of active recipients of the service under the DSA”, here: https://notes.nicfab.eu/en/posts/dsa-faq/ However, I don’t want to monopolize the newsletter 😊 Feel free

  89. pep.

    https://github.com/xsf/xmpp.org/pull/1254

  90. neox

    > neox: do you want to support the newsletter preparations outside of github this time? > > (other volunteers feel free) emus: yes, feel free to tell me what do to