XSF Communications Team - 2019-11-14

  1. Guus

    There is no such plan that I am aware of. You seem to be the only one that is interested in that.

  2. Nÿco

    I feel there is no need to rename Jabber planet to XMPP planet the two belong to the same era :) that said, maybe we can do some SEO

  3. Nÿco

    fyi, as an experiment: https://www.linkedin.com/feed/update/urn:li:activity:6600654130799304704

  4. Nÿco

    proposed tweet for today: " The November XMPP/Jabber newsletter is available in French! https://linuxfr.org/news/lettre-d-information-xmpp-01-octobre-2019-fosdem-2020-modernisation-de-xmpp-reseaux-de-pairs #OpenStandards #OpenSource #InstantMessaging #Chat " if no opposition, I'll post it

  5. DebXWoody

    The link is the october news not november.

  6. DebXWoody

    Is https://fosstodon.org/@xmpp managed by somebody here?

  7. SouL

    No one that I'm aware of

  8. pep.

    I don't think so?

  9. SouL

    I was on the hunt for a server where we could create a mastodon account, but I'm not decided yet

  10. SouL

    Setting up one can be a bit overkill for us, right now

  11. pep.

    SouL: we need mod_ap

  12. pep.

    And publish to microblog :p

  13. pep.

    This way we can use xmpp.org

  14. SouL

    That would indeed be really cool, also for us to show how cool XMPP is

  15. Nÿco

    > Is https://fosstodon.org/@xmpp managed by somebody here? I am experimenting it...

  16. Nÿco

    setting up a Mastodon server on our infra would be cool indeed, would show our implication and consistency however fosstodon is where Free/Libre/OpenSource Community is, so it seemed to me a good place to try it out

  17. DebXWoody

    Nÿco, Sehr cool!!!!

  18. Nÿco

    I've just set it up so far, please tell what you think

  19. SouL

    Nÿco, ah is it you? perfect then, thank you

  20. DebXWoody

    Nÿco, just post official information (Newsletter, maybe also information about state changes of XEPs,..) always use at least #XMPP #XFS. I think that is great.

  21. Nÿco

    XFS, eXtended File System? :)

  22. Nÿco


  23. DebXWoody


  24. Nÿco

    I confess I had never used Mastodon before... so far, after an hour of playing around, I... f***ing LOVE the federation concept... oh wait, what? :)

  25. pep.

    Tbh I spent like a month or two struggling to understand how to use it..

  26. pep.

    I would subscribe to people but I didn't even display the timeline for that :p

  27. pep.

    Also the columns are awkward to me. Scrolling horizontally is awkward

  28. Nÿco

    it is more or less like Tweetdeck as far as I can see

  29. pep.

    I don't use it

  30. pep.

    I don't use twitter..

  31. Nÿco

    some mobile clients exist, more or less like the basic mobile Twitter experience

  32. Nÿco

    problem: on https://wiki.xmpp.org/web/CommTeam there is: " Update the text here xmpp.org/participate/become-a-member/the-xsf-communication-team " but that page does not exist

  33. pep.

    It would be good to have a page for that indeed

  34. pep.

    Not just commteam but any team. That can be on the same page I'd say. Alongside "how to become an xsf member"

  35. pep.

    And then on each team we can redirect there

  36. Nÿco

    yeah, let's ask the webteam to do it! :)

  37. Nÿco

    nah, seriously, we can draft something... on the wiki or the website git repo

  38. Nÿco

    I made a thing: https://wiki.xmpp.org/web/Social_Media

  39. Nÿco

    and reminder: https://wiki.xmpp.org/web/Personas

  40. Nÿco

    Twitter metrics: (sorry, I have not been disciplined, I am a procrastinator)

  41. Nÿco


  42. Nÿco


  43. Nÿco

    for LinkedIn:

  44. Nÿco


  45. Nÿco

    Page (not Group)

  46. Nÿco

    proposed tweet for today (modified): " À tous les francophones, la lettre d'informations XMPP est disponible en français ! The November XMPP/Jabber newsletter is available in French! https://linuxfr.org/news/lettre-d-information-xmpp-01-octobre-2019-fosdem-2020-modernisation-de-xmpp-reseaux-de-pairs #OpenStandards #OpenSource #InstantMessaging #Chat " if no opposition, I'll post it in an hour or so

  47. Nÿco

    with this picture:

  48. Nÿco


  49. Nÿco


  50. Link Mauve

    Nÿco, don’t reencode PNG logos as JPEG.

  51. Link Mauve

    This makes them look ugly.

  52. Nÿco


  53. pep.

    Movim reencodes pngs to jpeg

  54. Nÿco

    I did not do that why do you say so?

  55. pep.

    Yes "you" did

  56. pep.

    Not you

  57. pep.

    Your client did

  58. SouL

    Why is that? Do you know?

  59. pep.


  60. Martin

    Might suchat.org be a good place for publishing the Spanish translations?

  61. Nÿco

    I can't judge...

  62. Neustradamus

    Any news for the bad link of the newsletter from 2019? - https://xmpp.org/2019/01/the-xmpp-newsletter-31-january-2018/

  63. Nÿco

    are you referring to something you "requested" ages ago somewhere?

  64. Neustradamus

    It is one of old remarks yes.

  65. Nÿco

    so what link? can you please submit a PR?

  66. Neustradamus

    A lot of tickets here: https://github.com/xsf/xmpp.org/issues

  67. Neustradamus

    Some were previously on tracker.xmpp.org ;)

  68. Nÿco

    which one? a PR would help

  69. Neustradamus


  70. Nÿco

    it's closed

  71. Neustradamus

    Not by me.

  72. Neustradamus

    https://xmpp.org/about/xsf/comm-team.html The team is not complete, some names are missing too ;)

  73. Neustradamus

    Like https://wiki.xmpp.org/web/CommTeam

  74. Neustradamus

    In the same time, can you update the logo of the newsletter/website/wiki/icon/twitter/mastodon/...? The logo is not good. The last perfect version is here: https://commons.wikimedia.org/wiki/File:XMPP_logo.svg

  75. Neustradamus

    -> https://github.com/xsf/xmpp.org/issues/608

  76. Nÿco

    what's wrong with the logo?

  77. Neustradamus

    Open your eyes

  78. Neustradamus

    Missing redirections: https://github.com/xsf/xmpp.org/issues/421

  79. Neustradamus

    The return of XEP Diff Tool: https://github.com/xsf/xmpp.org/issues/412

  80. Neustradamus

    XMPP Protocol Namespaces not complete: https://github.com/xsf/xmpp.org/issues/413

  81. Nÿco

    ok, you lost me now

  82. Neustradamus

    RFCs are missing and maybe not updated for actual: https://github.com/xsf/xmpp.org/issues/414

  83. Nÿco

    I understand you are benevolently reviewing lots of things

  84. Neustradamus

    Website missing redirections: https://github.com/xsf/xmpp.org/issues/419

  85. Neustradamus

    Registrar section is not updated: https://github.com/xsf/xmpp.org/issues/422

  86. Neustradamus

    Schemas section is not updated: https://github.com/xsf/xmpp.org/issues/423

  87. Neustradamus

    If no people look tickets, it is not good ;)

  88. Neustradamus

    Year after year

  89. Neustradamus

    Update history: https://github.com/xsf/xmpp.org/issues/635

  90. Link Mauve

    Neustradamus, what about contributing rather than reporting issues?

  91. Link Mauve

    You can see we’re all overworked already, you could help alleviate some of it.

  92. Neustradamus

    My tickets are very old, look when it was done.

  93. Link Mauve

    Yet you didn’t at any point step forward to fix them.

  94. Neustradamus

    Nÿco: For logos, you can look here: http://logs.xmpp.org/xsf/2019-11-12

  95. Nÿco

    PRs are better than issues generally also fresh is better than

  96. Nÿco


  97. Nÿco

    and here, we are only the commTeam

  98. Neustradamus

    Yes and you have forgotten my name in the CommTeam ;)

  99. Nÿco

    I have forgotten nothing related to this, as I am not supposed to maintain and know everything has your candidacy been approved by the Board? please point to the decision

  100. Nÿco

    > Update history: https://github.com/xsf/xmpp.org/issues/635 that was easy: https://github.com/xsf/xmpp.org/pull/636 can anyone review and merge?

  101. pep.

    Neustradamus: I can only reiterate what Link Mauve just said.

  102. pep.

    If it's an issue with git some other technical stuff I'm happy to take the time and teach you