Hello,
I have been recently reading about the "Chat Control" EU project.
For those interested, Tuta has a nice summary:
https://tuta.com/blog/chat-control-criticism
Reading the project, I have been surprised to see it could have deep consequences, not only for big messaging players, but for any chat hosting providers.
The idea is that all providers should be able to monitor and report traffic defined as prohibited by the state Coordinating Authority. Providers list include hosting service, interpersonal communications services, for example. I did not see any exemption in terms of platform sizes so I assume it could have a serious impact on XMPP server hosting.
I do not even see how it can be applied to an open protocol, given that you can connect to a server with any compliant client, we would have no way to enforce a backdoor for message scanning.
Have there been some discussion on that topic at the XSF ?
Is it really as catastrophic as it looks ? And if so, what should we do as members or as XSF ?
Thanks !
--
Mickaël Rémond
Hi all,
We have a date for FOSDEM 2026: January 31st to February 1st
This means we also have a date for Summit 28: January 29th - January 30th
As the person who has (co)organized the last two summits I would like
to start a discussion on the next summit by asking a few questions and
floating some ideas.
• How did you like the format of the last three summits? (Renting a
conference room in a hotel with lunch provided (in buffet style) by
the hotel)
• Do you have a concrete lead for some company or organization that
could provide us with a conference room for free in the city of
Brussels? I’m not asking for vague suggestions like "maybe someone
could try to reach out to xyz" I’m asking if you personally know
someone who has a key to a room.
• Do we want a 1 day or 2 day summit? Last year the 'official' part of
the summit was over after 1.2 days and had we known this we could have
probably managed to squeeze it all into one day.
• If we do a repeat of the last two (three) years (which i feel is
somewhat likely due to how difficult it is to find places that would
have us for free and because I’m under the impression that people like
the "fancy environment" with the snacks and the fancy bottles of
water) I feel somewhat strongly that we should switch to a model in
which every participant pays for their own seat (at per cost) and add
a fairly generous fee-waiver on top of it.
I’m very much in favor of keeping the Summit accessible.
(Socio)economicly speaking our community is very diverse. We have
people in our community who would not be able to come if they had to
pay the ~250 Euro the hotel charges us per person. But we also have
people in our community to whom this is a rounding error in the
overall travel+accommodation cost. (I have personally been on both
sides of this.)
The XSF notoriously doesn’t have a lot of money and efforts to change
this over the last 3 years haven’t been very successful. Switching to
a fee waiver model would allow board (or whoever) to set aside a fixed
amount and send x (where x=10 for example) applicants to the summit
for free.
cheers
Daniel
Hello,
another year went by and we have to get prepared to elect the 2025-2026
XSF Board and Council soon.
When you are interested in running for Board (business stuff) or Council
(technical stuff) for the upcoming term, please create an appropriate
Wiki page by November 2nd, 2025, 00:00 UTC and link it from here:
https://wiki.xmpp.org/web/Board_and_Council_Elections_2025
When you need to learn more about those roles, feel free to ask
questions on the list, our XSF chatroom, or contact people directly
which have been in those roles before.
Proxy voting is scheduled to start on November 3rd, and we will hold our
annual meeting to elect the next XSF Board and Council on November 20.
The meeting particulars are:
Date: 2025-11-20
Time: 19:00 UTC
Location: xmpp:xsf@muc.xmpp.org?join
Thanks,
Alex
I have created the XSF membership application page for Q4 2025 at:
https://wiki.xmpp.org/web/Membership_Applications_Q4_2025
The following XSF members have to reapply:
* Kim Alvefur
* Adrien Bourmault
* Dan Caseley
* Joachim Lindborg
* Georg Lukas
* Thilo Molitor
* Axel Reimer
* Peter Waher
* Stephen Paul Weber
* Yvo Meeres
Thanks,
Alex
Hello,
you can find our meeting minutes here:
https://wiki.xmpp.org/web/Meeting-Minutes-2025-09-04
A warm welcome to our new member Gonzalo Raúl. Feel free to introduce
yourself to the list and volunteer for one of our teams. You can find
some info on the XSF teams here:
https://xmpp.org/community/membership/
Also our annual board & council elections are upcoming. I will work on a
Wiki page and will start the process soon.
Thanks,
Alex
According to my records the following 20 XSF members have voted via
proxy in the current voting period:
* nicoco (at) nicoco.fr
* root (at) nicolosus.chat
* trần.h.trung (at) trung.fun
* gideon (at) xmpp.earth
* soul (at) blastersklan.com
* singpolyma (at) singpolyma.net
* badrihippo (at) disroot.org
* kobit (at) tigase.org
* mario (at) sabatino.pro
* eevvoor (at) jabber.fr
* nicola (at) nicfab.chat
* guus.der.kinderen (at) igniterealtime.org
* daniel (at) spacecloud.one
* martin (at) mdosch.de
* mathieui (at) mathieui.net
* holger (at) jabber.fu-berlin.de
* gnauck (at) conversations.im
* linkmauve (at) linkmauve.fr
* andrzej.wojcik (at) tigase.org
* tim (at) mailbox.bz
If you have not yet voted, please send a message to
xmpp:memberbot@xmpp.org.
If you have problems with memberbot please contact me directly by email
or xmpp.
Thanks,
Alex
I've started proxy voting via xmpp:memberbot@xmpp.org on the membership
applications listed here:
https://wiki.xmpp.org/web/Membership_Applications_Q3_2025
We will hold a member meeting on September 4th to formally approve the
voting results.
The meeting particulars are:
Date: September 4, 2025
Time: 19.00 UTC
Location: xmpp:xsf@muc.xmpp.org
When you have problems with memberbot please contact my directly by
email or xmpp.
Thanks,
Alex
I have created the membership application page for Q3 2025 at:
https://wiki.xmpp.org/web/Membership_Applications_Q3_2025
The following XSF members have to reapply:
* Travis Burtrum
* Martin Dosch
* Severino Ferrer de la Peñita
* Timothée Jaussoin
* Trevor Krahn
* Tobias Markmann
* Ralph Meijer
* Edwin Mons
* Emmanuel Gil Peyrot
* Peter Saint-Andre
* Holger Weiß
* Natalie Wirth
* Marvin Wissfeld
* Gideon White
Thanks,
Alex
Hello,
I came across the XMTP protocol (https://xmtp.org). It is a messaging protocol based on the blockchain, supported by Ephemera, a company with large fundings.
The protocol is presented as "XMTP (Extensible Message Transport Protocol) is the largest and most secure decentralized messaging network".
It seems to be confusing for the whole messaging community and I have a hard time imagining it is not on purpose.
Should we, as the XSF, make a move ? We could ask the IETF if they also would want to join a letter of clarification.
What do you think about it ?
Kind regards,
-- Mickaël Rémond
Hello dear XSF Members,
I see that we are still using "master" as the name of the main branch on Git
repositories (here, for instance: https://github.com/xsf/xeps ).
You are probably all aware that the use of this term has raised controversy in
recent years, as it can be perceived as a reference to slavery (see https://
en.wikipedia.org/wiki/Master%E2%80%93slave_(technology)#Controversy for
instance).
To avoid this unwanted reference and ensure the XSF is welcoming to everyone,
I propose that we change these branch names to "main," as many notable
projects have done (such as Python, the Linux Kernel, or GitHub).
I'm not sure whether this matter should be discussed in the Board or Council
(as it is a technical issue), but it would be good to add it to the agenda.
Thank you!
Goffi
