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
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
Hello,
you can find the meeting minutes here:
https://wiki.xmpp.org/web/Meeting-Minutes-2025-06-05
All applicants and reappliers were accepted.
You can find the updated memberlist here (once the PR is accepted):
http://xmpp.org/about-xmpp/xsf/xsf-member-list/
A warm welcome to all our new members. 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 a good start is our XSF channel when you have not joined it
already:
xmpp:xsf@muc.xmpp.org?join
Thanks,
Alex
According to my records the following XSF members have voted via proxy
in the current voting period:
* daniel (at) spacecloud.one
* emus (at) jabbers.one
* gnauck (at) conversations.im
* guus.der.kinderen (at) igniterealtime.org
* holger (at) jabber.fu-berlin.de
* kevin.smith (at) isode.com
* mario (at) sabatino.pro
* martin (at) mdosch.de
* nicola (at) nicfab.chat
* root (at) nicolosus.chat
* trần.h.trung (at) trung.fun
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
