XSF Communications Team - 2026-01-14


  1. badrihippo

    > badrihippo: you are still working on the handout? Apologies, was offline for a few days

  2. badrihippo

    I am doing it right now

  3. badrihippo

    Should I leave space for a map/location/something?

  4. emus

    > Should I leave space for a map/location/something? Im not sure what you have in mind? A map for what?

  5. badrihippo

    Sorry, I misread the conversation. gnemmi was tlaking about adding information about the stands at FOSSDEM. But I just realised that was for the blog, not for the flyer

  6. badrihippo

    Sorry, I misread the conversation. gnemmi was talking about adding information about the stands at FOSSDEM. But I just realised that was for the blog, not for the flyer

  7. emus

    badrihippo: but you are still able to do the design?

  8. badrihippo

    Yes emus I'm working on it now. Sorry for the delay!

  9. Ge0rG

    so, who's coordinating what we show at the FOSDEM? Do I need to bring a TV? The LED lights? Cameras? I could print a bunch of A4-sized flyers (color laser, not the super-best quality)

  10. MattJ

    There isn't much coordination, generally. People show up with demos/materials and we make it work.

  11. MattJ

    If the TV is large and would go on the table, I'd worry it might consume too much space (compared to just having a laptop open, for example)

  12. MattJ

    If it has a stand and could go behind the table, maybe

  13. Ge0rG

    it's a 47" TV that needs to be put on a table, I don't have a dedicated stand for it

  14. Ge0rG

    the base is maybe 25cm deep, but I see the point (and I'm not at all opposed to leaving the TV at home)

  15. MattJ

    Yeah, my feeling is that's a bit large to have on the table

  16. Ge0rG takes it off the table now.

    πŸ˜‚ 3
  17. badrihippo

    First draft of the XMPP Ecosystem Highlights flyer

  18. badrihippo

    https://disroot.org/upload/019bbc4d-1c13-7d2f-9f37-f977e971b437/xmpp-highlights-2025-draft1.pdf

  19. badrihippo

    I'm making it a foldable layout as described in the Scribus wiki. Since this is very confusing onscreen, I'll also make a non-printable version to share online

  20. badrihippo

    https://disroot.org/upload/019bbc4d-a81f-790c-8e16-f4706242de51/31428562-7e7b-4a77-aa89-72683241ed0b.png

  21. badrihippo

    I have *not* done any editing of the text or design besides setting the fonts. Will do that and add screenshots in a bit!

  22. badrihippo

    I'm also considering having Movim improvements as just one long update, since there are three of them? Maybe with subheadings to highlight the calls and screensharing bits

    πŸ‘ 2
  23. Ge0rG

    So this is the XMPP FOSDEM Gazette? Cool

  24. Ge0rG

    Is it separate from the "what is XMPP and how do I get it" flyer?

  25. badrihippo

    I suppose so, because it doesn't have much information about what exactly XMPP is πŸ˜…

  26. badrihippo

    Is anyone making the "what is XMPP" flyer or do y'all want me to make that too?

  27. badrihippo

    https://disroot.org/upload/019bbc65-5186-78ee-83b3-da4310f4f5c1/xmpp-highlights-2025-draft2.pdf

  28. badrihippo

    Lookin' better with a few logos and screenshots?

  29. goffi

    I'm checking the flyer, this is false: ``` Movim becomes first XMPP client to support multi- participant calls ``` At least Dino and Libervia were implementing it long before Movim.

  30. Ge0rG

    badrihippo: I haven't been involved in anything, so I don't know if anybody is making a "what's XMPP" flyer. But we should have that, or have both in one.

  31. goffi

    And as side note, I'm not really found of "first to do XXX" marketing, this is really putting XMPP ecosystem in competition.

  32. goffi

    Libervia is also going through major redesign, which hopefully will be ready for FOSDEM. I can send a screenshot.

  33. badrihippo

    > I'm checking the flyer, this is false: > ``` > Movim becomes first XMPP > client to support multi- > participant calls > ``` > At least Dino and Libervia were implementing it long before Movim. Oops. I was going by what was written in the pad ("First ever XMPP client to support multi-participant calls.") though fwiw even I was wondering "wait, didn't Dino do that already?"

  34. goffi

    Yeah, that absolutely not true.

  35. goffi

    Dino and Libervia have MUJI (MESH), and Libervia has SFU based component (even going to work on it with Movim actually). And I think that OpenFire people and other teams have worked on stuff too.

  36. badrihippo

    What about "Simultaneous webcam and screen sharing comes to XMPP" which also talks about Movim?

  37. goffi

    TBH Libervia is not in production ready state, that's why I'm not advertising multi-party calls that much, but it's there.

    πŸ‘πŸ½ 1
  38. Kris

    That is a browser feature, but Dino doesn't support that afaik.

  39. goffi

    Simulatenous I think that only Movim does it so far (Libervia does desktop screensharing, but replacing webcam stream at the moment)

    πŸ‘πŸ½ 1
  40. badrihippo

    > And as side note, I'm not really found of "first to do XXX" marketing, this is really putting XMPP ecosystem in competition. Maybe "...comes to XMPP" is a better framing? And if multiple clients introduced it in the same year we can include all of them

  41. goffi

    But again, I really think that "first to do XXX" is unhealthy marketing. Working together is a strengh of XMPP IMO.

    πŸ‘πŸ½ 1
  42. arne

    We could also add one short news for each client to make it more fair. I guess Cheogram, monocles chat, Monal and others had also updates

  43. goffi

    It's not the same year, I did implementation something like 2 years ago, and Dino had already MUJI at the time (I've tested with it).

  44. goffi

    Just saying that Movim implement multiparty call is enough.

    πŸ‘πŸ½ 1
  45. goffi

    Yeah, would be more fair indeed. All clients have neat things.

    πŸ‘ 1
  46. goffi

    The goal is to show activity and cool feature are implemented, right?

  47. badrihippo

    Yeah

  48. goffi

    I thing that many clients have added reactions this year too (or it was already the year before?).

  49. badrihippo

    Maybe we can frame it as "reactions have become very widespread now"?

  50. goffi

    On the specs side there also exciting things. A flyers will be too short πŸ™‚

  51. badrihippo

    Let me try to check the dates though. Maybe it's time to take a break from typesetting and figure out the content a bit more first

  52. arne

    Just suggesting monocles chat got a vcard profile editor and a vcard qrcode sharing besides many other things

  53. arne

    Just suggesting monocles chat got a vcard profile editor and a vcard QR code sharing besides many other things

  54. badrihippo

    > On the specs side there also exciting things. A flyers will be too short πŸ™‚ How about we have one for software updates/features which will have more space for everyone, and one for other things (specs, initatives like the providers file, etc.)?

  55. Ge0rG

    also we need something for DI.DAY

  56. badrihippo

    Here's the pad where I got my content from btw: https://pad.nixnet.services/x87ng-viRoGzVtjeIv7Luw

  57. arne

    > also we need something for DI.DAY Was DI.Day 2025?

  58. badrihippo

    Maybe we can all add ideas there (like the vcard improvements you mentioned arne) and we then look again to see what/how to include it all?

  59. Ge0rG

    arne: it was introduced at 39c3, but we should have some material regardless of the year

  60. Ge0rG

    arne: it was introduced at 39c3 in december, but we should have some material regardless of the year

  61. Ge0rG

    also from 39c3, probably worth a mention in the 2025 flyer: https://blog.mathieui.net/xmpp-and-metadata.html

  62. badrihippo

    Speaking of 39c3, does anyone have a higher-res version of this picture (or similar)? I thought it'd be cool to make the "front cover" and "back cover" of the flyer dark and have this at the bottom of the back cover

  63. badrihippo

    https://disroot.org/upload/019bbc78-5f8b-7bc9-8e3c-4fc336dc4de6/39c3.jpg

  64. goffi

    > Here's the pad where I got my content from btw: https://pad.nixnet.services/x87ng-viRoGzVtjeIv7Luw With vacations, I haven't had really time to check that. I can add some stuff I've worked on. What is the deadline?

    πŸ‘πŸ½ 1
  65. badrihippo

    You'll have to ask emus but my guess is we still have time?

  66. Ge0rG

    no details in https://wiki.xmpp.org/web/Conferences/Summit_28#Promotion_material

  67. badrihippo

    On a related note, if it's more convenient feel free to text here with the phrase highlight2025 (one word). I can come back and do a search for that at some point to add them all to the pad πŸ˜‰

  68. badrihippo

    That way we can also discuss the things before finalising it

  69. goffi

    Are all teams aware of that pad? Wouldn't a quick announcement on standard@ help? Also we were talking about 30s presentation for each project willing do to a small video, but I don't know if it will be thing or not at the end.

    πŸ‘ 1
  70. arne

    I just added some things. Do you think we should better sort it by each client and not by month?

    πŸ‘ 1
  71. badrihippo

    Yeah that makes more sense, that way we can just have one update per client. Maybe include the month information if you have it so it's easier to find in the newsletter (but if you have a link to a blog post or something that also works)

    πŸ‘ 1
  72. badrihippo

    So that I can find more information while writing the update

  73. emus

    > Is it separate from the "what is XMPP and how do I get it" flyer? The what?

  74. emus

    badrihippo: ideally keep it short so we get sufficient enough and diverse information there

  75. Ge0rG

    emus: there is a flyer "xmpp highlights of 2025", but I think we also need a flyer "what's XMPP and how do I get it installed & configured". Or we need to have both in one.

  76. emus

    > You'll have to ask emus but my guess is we still have time? Well, Im planning to print this in Brussels with the service that Matt suggested

  77. emus

    > emus: there is a flyer "xmpp highlights of 2025", but I think we also need a flyer "what's XMPP and how do I get it installed & configured". Or we need to have both in one. I would like to link the getting started page

  78. emus

    > There isn't much coordination, generally. People show up with demos/materials and we make it work. Yes, but Im trying to get things align as early as possible.

  79. emus

    > Ge0rG takes it off the table now. I dont know what the new location will tell. i dont want to say bring it just to say we dont have the space. Also, what can we show? Nobody really came up with client promotion or so. Ralphm usually brings a small TV right already?

  80. ralphm

    No, I only have a projector

    πŸ‘ 1
  81. goffi

    emus, Which service? I'll maybe print some stickers, but last time I wanted to do it in Brussels it was crazy expensive.

  82. Ge0rG

    projector is even better. can I add the Easy XMPP video into the rotation... it's from 2020, but still works

    πŸ‘ 1
  83. ralphm

    goffi: for stickers, use StickerMule

  84. goffi

    > goffi: for stickers, use StickerMule thanks

  85. MattJ

    The projector doesn't traditionally have a "rotation", it streams social media mentions. But maybe we could work something out (afaik it still needs updating with Mastodon support)

  86. gnemmi

    Holy cow!. I can't remember when was the last time I saw so much activity on the MUC! Will try to catch up on the backlog and reply as I go over the messages

  87. gnemmi

    > I'm also considering having Movim improvements as just one long update, since there are three of them? Maybe with subheadings to highlight the calls and screensharing bits There are three of them reflects that edhelas kept adding features non stop every month. I don't think it deserves to be sandwiched into a long update as if it was the result of one long coding sessioin. It also reflects the fact that every month has a highlight and that the Newsletter is something that's worth keeping up with and read every month. Following the same logic, we could also start doing long releases, slow down the Newsletter and publish one every three or four month ...

  88. gnemmi

    > Is anyone making the "what is XMPP" flyer or do y'all want me to make that too? Not that I know of .. I don't remember anyone proposing it

  89. Ge0rG

    IMHO, a "what is xmpp and how do I get it" flyer is as important as the "what have we done in the last year", covering a different audience. There is a big DI.DAY initiative in Germany to regain digital sovereinity, and we (the XMPP promoters, maybe even we the XSF) need to take it up and be prepared. There will be a significant audience coming from Germany

    πŸ‘ 1
  90. gnemmi

    > I'm checking the flyer, this is false: > ``` > Movim becomes first XMPP > client to support multi- > participant calls > ``` > At least Dino and Libervia were implementing it long before Movim. I can fix that right away.

  91. gnemmi

    I just did: "Movim gains support for multi-participant video calls."

  92. Ge0rG

    MattJ: so fediwall for #xmpp and #fosdem then? I could wire my cameras to post to ~facebook~ mastodon with those tags

  93. Ge0rG

    but posting to a MUC would be even cooler obviously

  94. MattJ

    For sure :)

  95. MattJ

    Ralph's thing reads from pubsub, so if you put stuff in pubsub... :)

  96. MattJ

    (not sure what format, but I'm guessing it might be atom)

  97. badrihippo

    > It also reflects the fact that every month has a highlight and that the Newsletter is something that's worth keeping up with and read every month. Following the same logic, we could also start doing long releases, slow down the Newsletter and publish one every three or four month ... Thanks for pointing this out, because I somehow lost sight of the fact that part of this is to draw attention back to the *newsletter*

  98. Ge0rG

    MattJ: uuuh, I don't have that. All I have is `aioxmpp/examples/upload_muc.py`

  99. badrihippo

    > It also reflects the fact that every month has a highlight and that the Newsletter is something that's worth keeping up with and read every month. Following the same logic, we could also start doing long releases, slow down the Newsletter and publish one every three or four month ... Thanks for pointing this out gnemmi, because I somehow lost sight of the fact that part of this is to draw attention back to the *newsletter*

  100. gnemmi

    > And as side note, I'm not really found of "first to do XXX" marketing, this is really putting XMPP ecosystem in competition. So honestly and really sorry about thata goffi! I 100% honestly never meant it to be read in that way. The idea was to convey the fact that XMPP client developer work non stop to add new features and implement the latest XEPs! .. I spirit of letting everyone know that XEP are not just tigers on paper but actual the description of features that actually *do* get implemented by developers!

  101. gnemmi

    Still. This was about 2025 highlights

  102. badrihippo

    > Yeah that makes more sense, that way we can just have one update per client. Maybe include the month information if you have it so it's easier to find in the newsletter (but if you have a link to a blog post or something that also works) Sorry arne I take this back, I think we should continue sorting by month if the focus is on the newsletter. It's a sortof month-by-month "this is what happened in XMPP this year" rather than a comprehensive client-wise breakdown, am I right gnemmi?

  103. gnemmi

    > TBH Libervia is not in production ready state, that's why I'm not advertising multi-party calls that much, but it's there. Exactly! This was more geared towards what was announced during the span of 2025

  104. gnemmi

    > We could also add one short news for each client to make it more fair. I guess Cheogram, monocles chat, Monal and others had also updates Absolutely! The pad was there so everyone could add their own highlights righ off the bat!

  105. goffi

    gnemmi, I wasn't saying that to accuse anybody at all, it's just that I find from time to time (I may have even used that myself in the past actually, I don't remember) this "XXX implemented YYY first", and I nowadays think that it's not great (as said above, if feels about competition). I'm not pointing finger at anybody, sorry if it looked like that.

    πŸ€— 1
  106. gnemmi

    The bad thing was that it never happened, and I ended up being the only one who actually sat down to do the whatever work I could do

  107. goffi

    The remark was just a general side note, not about those highlights in particular.

  108. gnemmi

    > The goal is to show activity and cool feature are implemented, right? During 2025

  109. MattJ

    FWIW in the version I did, it was simply a discussion point, to show XMPP is not "dead" as some people claim. Show all the activity that has been happening. I also specifically chose things that demonstrate XMPP's capabilities. For example, I picked the news about Dino implementing video calls because back then people assumed XMPP couldn't do video calls. I wrote about Slidge because people thought only Matrix supported bridges to other networks, etc.

  110. MattJ

    It wasn't just "In this month, this happened..."

  111. badrihippo

    That sounds like a good way to go about it

  112. gnemmi

    > On the specs side there also exciting things. A flyers will be too short πŸ™‚ Absolutely. 2025 was a really interesting year in re specs. But the highlights were more end user targeted .. or so I thought

  113. badrihippo

    On a slightly unrelated note, I've been toying with the idea of doing a "specs watch" which is a sort of running commentary on where spec development is at, or maybe examples of what some new XEP could be used for

  114. gnemmi

    > Just suggesting monocles chat got a vcard profile editor and a vcard qrcode sharing besides many other things Please do! That one absolutely scaped me as I was dealing with the closing of the Newsletter and .. well .. all the end of the year and holidays obligations .. so, yeah .. I was kinda overwhelmed

  115. MattJ

    If it's not purely chronological, then I would put a section that is about the specs. Pitch it as work that is being done for clients/etc. to implement in the future.

    πŸ‘ 1
  116. badrihippo

    > On a slightly unrelated note, I've been toying with the idea of doing a "specs watch" which is a sort of running commentary on where spec development is at, or maybe examples of what some new XEP could be used for I haven't figured out yet what this would look like or what the target audience would be, but perhaps this would also help with the discussion Daniel initiated on the mailing list and later in the main channel about having more particpation in last calls

  117. badrihippo

    > If it's not purely chronological, then I would put a section that is about the specs. Pitch it as work that is being done for clients/etc. to implement in the future. How about a "looking to the future..." listing the updates and their potential use-cases? And ending on a note that maybe we'll look back and see some of those in clients next yeat!

  118. badrihippo

    > If it's not purely chronological, then I would put a section that is about the specs. Pitch it as work that is being done for clients/etc. to implement in the future. How about a "looking to the future..." listing the updates and their potential use-cases? And ending on a note that maybe we'll look back and see some of those in clients next year!

  119. MattJ

    Yep

  120. MattJ

    Sounds like a great idea :)

  121. gnemmi

    > > also we need something for DI.DAY > > Was DI.Day 2025? It was c3c9 .. and it sparked a small discussion on the XSF Discussion MUC

  122. gnemmi

    > Are all teams aware of that pad? Wouldn't a quick announcement on standard@ help? Also we were talking about 30s presentation for each project willing do to a small video, but I don't know if it will be thing or not at the end. They should be. emus did an open call for everyone to collaborate with their own highlights.

  123. gnemmi

    I ended up being the only one who picked up the gauntlet ..

  124. gnemmi

    > I just added some things. Do you think we should better sort it by each client and not by month? My humble opionion?: month .. for the same reasons that I exposes in re Movim. It's better for the projects and it's better for the Newsletter

  125. Ge0rG

    cal0pteryx: is it possible to pre-select filters on https://providers.xmpp.net/ using hashtag magic? I'd like to link to a list only showing IBR providers hosted in the EU with a bus factor > 1

  126. gnemmi

    Done with the backlog! Super happy to see all of you getting involved with Comm activities! πŸŽ‰πŸ€—πŸŽ‰

  127. badrihippo

    > I ended up being the only one who picked up the gauntlet .. Maybe we can put out a call again but also sharing my in-progress PDF this time? Nothing like "seeing a printed flyer taking shape with your favourite highlights left out" to spark discussion πŸ˜‰

  128. badrihippo

    Only half joking, but it might be worth putting out that call again saying we're starting to put things together?

  129. gnemmi

    > Sorry arne I take this back, I think we should continue sorting by month if the focus is on the newsletter. It's a sortof month-by-month "this is what happened in XMPP this year" rather than a comprehensive client-wise breakdown, am I right gnemmi? In my personal and humble opinion .. yup

    πŸ‘πŸ½οΈ 1
  130. gnemmi

    > gnemmi, I wasn't saying that to accuse anybody at all, it's just that I find from time to time (I may have even used that myself in the past actually, I don't remember) this "XXX implemented YYY first", and I nowadays think that it's not great (as said above, if feels about competition). I'm not pointing finger at anybody, sorry if it looked like that. goffi, mate, I know you meant no harm and that what you say is never ill intentioned! No harm done *at all*!!

  131. gnemmi

    > FWIW in the version I did, it was simply a discussion point, to show XMPP is not "dead" as some people claim. Show all the activity that has been happening. I also specifically chose things that demonstrate XMPP's capabilities. > > For example, I picked the news about Dino implementing video calls because back then people assumed XMPP couldn't do video calls. I wrote about Slidge because people thought only Matrix supported bridges to other networks, etc. Exactly!!. That was the whole point of writing a 2025 highlights! πŸŽ‰πŸ€—

  132. gnemmi

    > FWIW in the version I did, it was simply a discussion point, to show XMPP is not "dead" as some people claim. Show all the activity that has been happening. I also specifically chose things that demonstrate XMPP's capabilities. > > For example, I picked the news about Dino implementing video calls because back then people assumed XMPP couldn't do video calls. I wrote about Slidge because people thought only Matrix supported bridges to other networks, etc. Yeah .. that was the reason why I added Slidge 3.0 as a highlight

  133. badrihippo

    > IMHO, a "what is xmpp and how do I get it" flyer is as important as the "what have we done in the last year", covering a different audience. There is a big DI.DAY initiative in Germany to regain digital sovereinity, and we (the XMPP promoters, maybe even we the XSF) need to take it up and be prepared. There will be a significant audience coming from Germany FWIW, I don't mind designing this as well, although someone else will have to manage the physical part (i.e. getting it printed and distributed to wherever it's supposed to go)

  134. gnemmi

    > > If it's not purely chronological, then I would put a section that is about the specs. Pitch it as work that is being done for clients/etc. to implement in the future. > How about a "looking to the future..." listing the updates and their potential use-cases? And ending on a note that maybe we'll look back and see some of those in clients next year! This sounds pretty much like it .. as it would heavily depart from 2025 highlights ..

  135. badrihippo

    (And in English, though if someone provides a German language version I typeset that as well)

  136. gnemmi

    > Only half joking, but it might be worth putting out that call again saying we're starting to put things together? Sure!. Unless emus thinks otherwise. The pad is still open and you are still working on the your PDF ... so I don't see why not ( unless we are dealing with some time constraints ). The whole thing was never meant to be a "me" thing, just as I stated on the XFS MUC back when we discussed this

  137. arne

    badrihippo: I thought that the list then maybe gets to full when sorted by Month? But of course you can try it out. Maybe it looks better

  138. cal0pteryx

    Ge0rG: not yet, but I see what I can do :)

  139. Ge0rG

    cal0pteryx: a few days ahead of FOSDEM would be great

  140. emus

    > emus, Which service? I'll maybe print some stickers, but last time I wanted to do it in Brussels it was crazy expensive. MattJ can you drop the printing service you used back then? I don't have it at hand right now.

  141. MattJ

    "Plan 2000" @ ChaussΓ©e de Charleroi 197a

  142. MattJ

    https://www.plan2000.be/

    πŸ™ 1
  143. emus

    > > I just added some things. Do you think we should better sort it by each client and not by month? > My humble opionion?: month .. for the same reasons that I exposes in re Movim. It's better for the projects and it's better for the Newsletter It's highlights. we should expose the time. but rather go for hightlight that is more connected to usability than sorting by time.

    πŸ‘ 1
  144. gnemmi

    badrihippo, ☝️

  145. emus

    > cal0pteryx: is it possible to pre-select filters on https://providers.xmpp.net/ using hashtag magic? I'd like to link to a list only showing IBR providers hosted in the EU with a bus factor > 1 Making a TOP listed EU server excerpt would be great!

  146. Ge0rG

    Come to the EU! We have ~cookies~ ~cookie banners~ GDPR

    πŸ˜„ 1
  147. emus

    We have GDPR and the good cookies πŸͺ

  148. edhelas

    We need a GDPR Cookie Banner in XMPP clients πŸ‡ͺπŸ‡Ί

    ❗ 1