XSF Communications Team - 2026-01-27

Évelyne: sorry I had to leave. I'm back here now 😃

> hm, what i could do to show how that'd work is to analyze a document. The fosdem flyer would be a good one If I may, you could also analyze any of the XMPP Newsletters, which are actually our main product ( as the Communication Team )

You can find them in here: https://xmpp.org/categories/newsletter/

Or our blog post: https://xmpp.org/blog/

Well i had found an interesting repeating theme in the flyer: that of (XMPP software) creating connectivity (between protocols, documents, people) that seems quite important. I was drawing over the blurb for libervia's mailing list to XMMP forums but had a software issue and have to start over (it's not terribly complicated at least)

Well that may be because we still haven't had time to take on the ( soon to be ) repeating theme about connectivity between Movim ( XMPP social network ) and Monocles Chat ( XMPP client ) creating human interactions 😃

i find it interesting because it could be that the construct "connecting" is also used to direct software development. That would be something to look into at least.

Indeed

for comparison you have the construct "modern" on hyped github repos that has no context-independent semantics, and seems to be about internalizing some recent trends

or JSON schemas can be seen as modern, while XML schemas won't be, although the former draws a lot from the latter

I have to admit that I'm really hyped about your take on connectivity in terms of a construct ✏

Did you by any chance get to read the article about why XML instead Json?

from the XSF website? I think so, but I also just read a lot about XML recently

Évelyne: https://www.process-one.net/blog/stop-telling-us-xmpp-should-use-json/

I found this one to be particularly interesting ( XMPP - ActuvityPub ) even if it's not strictly XML related: https://mov.im/community/pubsub.movim.eu/Movim/the-difference-between-xmpp-and-activitypub-explained-through-the-blog-feature-Hdx4FR

gnemmi: here's how I'd look at the first blurb in draft 10 of the flyer for the FOSDEM, to get an idea of that kind of approach works on a tiny case.

https://mendous.se/xmpp/share/8bbd4818-8c25-4da9-a07a-261cce5524f3/micro-analysis-libervia-blurb.png

Nicely done ...

"much work" would have been one to account for, but i didn't have enough room

I have to come again to you and tell you I find your idea excitingly interesting

Just as I told you in the las Chat of the Future session

also you can see how the fact "XMPP can bridge with email" is being constructed bit by bit: here libervia can convert mailing list into its own system. If this went on and became an oft implemented feature, you could say "XMPP allows to upgrade your mailing lists" as a general truth

Arguably so .. yes

I think I can follow your train of thought so far. And I have to say I like it

so far it's dutifully applied actor-network theory, helped by the practice of text analysis (the pioneers of ANT weren't too good at it compared to semioticians proper)

I can also see how analyzing this constructs from such a deep level and perspective would have a profound impact from a communicational point of view

in my opinion this kind of approach really helps with finding *adequate* actions and making adequate artifacts (texts, software…): you know what's in the context well, so avoid redoing what exists, and adapt to exactly what's needed. It's kind of like having a good design document in software development, you avoid incompatiblities, drifts of semantics between teams, and can share work better.

This could have a direct impact in XEPs development

And particularly, of course, in the XMPP as the underlaying foundation of a software ecosystem

yes, hopefully it could positively impact the XMMP system 🙂

I'm really looking forward to whatever it may be that you can put together so we ( or at the very least I ) can get a deeper understanding of your goal to help you better

> badrihippo is the final version in pdf sent already? Not yet emus, I will add the credits, QR code, and newsletter/mailing list promotions and share it in a couple of hours ↺

Évelyne, as gnemmi mentioned I too am busy with FOSDEM at the moment (creating the flyer) but what you're doing sounds really interesting! I'm yet to completely wrap my head around it but this kind of "taking a step back and understanding what XMPP is" beyond technical terms seems like something that'd be quite beneficial for XMPP. I'll probably understand it better as the conversation progresses 🙂

> that's a possibility, i'm just cautious since i know jargon or complexity can cause various negative reactions I would personally be patient about clarifying things if needed, but it's true that discussions can get intense at times which could get overwhelming ↺

Maybe this room would be calmer compared to the main room since it's clear the focus is on communication? And we'll all be here to help you! emus gnemmi what do you think?

> badrihippo, maybe merge all three news about Movim, and all three news about Libervia? Hi Link Mauve! The decision was made to keep them separate because they happened at various times through the year ↺

But that reminds me, I should probably mention the month somewhere as otherwise the ordering doesn't really serve a purpose

arne, were the four Monocles updates in the same version? If not, I could spread them out too (especially as we have the space)

>> badrihippo, maybe merge all three news about Movim, and all three news about Libervia? > Hi Link Mauve! The decision was made to keep them separate because they happened at various times through the year Oh was it, havent recognised... I actually thought by client sections would be better too. ↺

I would actually say we should have one entry per client, not multiple. Its confusing to normaler users I believe. Sorry, I was not looking at that.

> hello everyone, I have a question > > **Context**: during the "chat of the future" sessions I have offered doing a kind of ethnographical work about the XMPP ecosystem. Some expressed strong interest. This work would be about tracing the mental maps that people in the XMPP ecosystem use to understand and orient themselves inside said ecosystem. The point would be to then produce a very simplified, user-centric map, and another for those wanting to contribute more deeply. > > **Question**: When would be the best time to have a brief discussion about this, to get an idea of what's doable, and if it would fit actual needs? I know you're busy with FOSDEM atm. Would doing that in this chat be fine? > > I'll be happy to provide details about the kind of work I have in mind if there's a discussion. Thanks for proposing. Sounds interesting. I think before any discussion it would be good to better understand what such a user-centric map would look like in a practical way. Maybe you can prepare an example. Other than that, lets postpone this after FOSDEM and after the next session, 3rd Feb. Maybe I can find a slot for presenting your idea there. Another question would be where do you get the data from? But lets postpone here a bit. Lots of stuff going on. ↺

Oops, looks like my last attachment didn't get uploaded

It's on a different machine; I'll re-send it in a bit

> It's on a different machine; I'll re-send it in a bit Can we upload it somewhere on a link? Maybe you can make a PR to the Github repo? ↺

Do you mean the XMPP website repo?

I can do that, though the PDF renders are going to be new blobs in each commit. I suppose we can squash before the final merge

On a related note, are we planning to publish these highlights as a blog post as well? Ge0rG was suggesting having it there with links that people can click through for more information (either that, or make a set of links like https://fosdem.xmpp.link/) ✏

Yes 🤔 hmm, okay no good idea. Any temporary fileshare (privacy-respecting)? It would be good to ensure where the latest file is. Maybe I can offer a folder in my nextcloud for the moment

Actually, I have a nextcloud too! I could do it in that

> Actually, I have a nextcloud too! I could do it in that Ah okay ↺

https://disroot.org/upload/019c003d-4e8a-76bd-9af6-5fc708023b1d/xmpp-highlights-2025-draft11.pdf

Latest version that might not have got uploaded last time. This has dates emus but if think it's better I can get rid of those and group things client-wise instead? Just take a look and let me know

Setting up NextCloud now so y'all will always have the latest version

badrihippo, emus: let me know about the redirect / landing page with all the "clickable links" :)

In the meantime, here's the full source! I usually render the PDF whenever I finish working, so that'll be the latest too (I did a print one as well this time)

https://cloud.thekambattu.rocks/s/LiELKHr6AHAgQa2

Side note: since Scribus documents are XML, I wonder if we'll be able to magically share them as live updates through XMPP one day 🙃

> https://cloud.thekambattu.rocks/s/LiELKHr6AHAgQa2 Its just great! MattJ would you liked to be referenced here? You had the inital design right? Then I would just say, put the contributors in alphabetical order, and join the first three into XSF Communication Team. From then I would say lets call a freeze. We put many efforts. Unless you see wrong content its very much good to go and leftover resources should be invested else where. Special thanks to you gnemmi and badrihippo! ↺

> badrihippo, emus: let me know about the redirect / landing page with all the "clickable links" :) Sorry, help me with the context again? ↺

Di.day? ✏

Awesome! I'm making the changes now

This is about the same FOSDEM newsletter. Basically, Ge0rG offered to host a "place to point the QR code at the back of the flyer" which could have all the clickable links for the mentioned news items

> Sorry, help me with the context again? In reply to this ^ ↺

Two ideas were: a landing page on xmpp.link similar to the Di.day one, or we can publish the highlights as a full newsletter entry on the blog and direct the QR code there

The QR code in the current flyer points to https://fosdem.xmpp.link/ which we can either update with the correct content or redirect to a blog post (and, as Ge0rG pointed out, we can always start with one and change it later)

> The QR code in the current flyer points to https://fosdem.xmpp.link/ which we can either update with the correct content or redirect to a blog post (and, as Ge0rG pointed out, we can always start with one and change it later) Ge0rG, though I support the Di.day initative Could we move the banner a bit down and come with the most important, the apps right away? It think it may confuse the general audience of this handout. You will also have the separate DiDay handout. What do you think? ↺

Other then that the link is good

Georg is there a font without serifs? But its just my taste

emus: give me a markdown file with the anticipated content, a html file (or directory) or a URL to point to

emus: the current content ist based on the di.day material, and only has the di.day links

> emus: give me a markdown file with the anticipated content, a html file (or directory) or a URL to point to So you want to make a separate link? ↺

emus: the source file is https://codeberg.org/ge0rg/fosdem-2026-xmpp-diday/src/branch/main/index.md and uses PanAm CSS (linked at the bottom)

emus: it is a separate link, https://fosdem.xmpp.link/ for the XMPP 2025 flyer and https://di-day.xmpp.link/ for the DI.DAY flyer

emus: if you make a blog post for the "what's new in 2025", I will redirect to that, otherwise, give me something to host there.

unfortunately, I don't have the time to do that myself :)

> https://cloud.thekambattu.rocks/s/LiELKHr6AHAgQa2 I've updated the credits here. And added MattJ as well (but let me know if you *don't* want to be credited!) ↺

> emus: if you make a blog post for the "what's new in 2025", I will redirect to that, otherwise, give me something to host there. Would anyone else be motivated to propose? I can try, but there is so much stuff to do at the moment. ↺

I could do it emus. I'm guessing it'll be more or less the same content from the flyer pasted into the newsletter (and links added)?

> I could do it emus. I'm guessing it'll be more or less the same content from the flyer pasted into the newsletter (and links added)? Possibly yes. Maybe start with the apps and some more. Then the articles? ↺

for after the fosdem I invite everyone to make the highlights also a blogpost.

We can add some more information from the pad

Okay, at least the blinken-LEDs are ready now. https://chaos.social/@ge0rg/115968332190390588

Ge0rG: this is just great and already sufficient!

We need more logos!!1

emus: I wanted to have a real XMPP to LED bridge

emus: nobody stepped up when I asked for logos. I need 32x32 on black background with gamma tuned down for better contrast

> emus: nobody stepped up when I asked for logos. I need 32x32 on black background with gamma tuned down for better contrast Can you put that request again into the XSF channel and under your toot? ↺

emus: feel free to do the former, and the latter doesn't make sense. The target audience are people involved in FOSDEM preparation, not internet randos

In fact, I'd like to limit the logos to the projects actually present there / mentioned in the DI.DAY flyer

I don't want to explain to people why it's not a good idea to add Pidgin to the rotation.

Did you just called us internet randos?! 😃😉 ↺

emus: no, only the people outside of this room 😉

Thats okay!! ☝️ ↺

in re the credits on the leaflet, it should be:

Created by XSF Communication Team Special thanks to: Arne, Badri (badrihippo), Ge0rg, Jérôme Poisson (Goffi) and MattJ

"Stay connected in 2026! Hear about events as they happen by subscribing to the XMPP Newsletter" ->

Stay connected in 2026! Subscribe to the **XMPP Newsletter** to stay up to date about news and recent developments within the XMPP ecosystem. ✏

> Created by > XSF Communication Team > > Special thanks to: > Arne, Badri (badrihippo), Ge0rg, > Jérôme Poisson (Goffi) and MattJ Let's leave it as it is gnemmi and not take too much space. ↺

> Stay connected in 2026! > Subscribe to the **XMPP Newsletter** to stay up to date about news and recent developments within the XMPP ecosystem. That's okay ↺

> Let's leave it as it is gnemmi and not take too much space. Space is the last of my concerns when proper attribution is not duefully dealt ↺

But, that's ok, it's your call

Let's do it like in the newsletter for the moment, ok?

The Newsletter is the main product of the Comm Team, and we thank duefully thank our contributors

Not the other way around

Yes, but it's hard to disting everyone contribution, so we have just take the order alphabetically. We can discuss this in the future for sure.

Sure!

I don't insist on attribution