XSF Communications Team - 2025-02-24

https://fabionatali.com/posts/xmpp-self-hosting-tutorial/

Kris, - [XMPP self-hosting tutorial](https://fabionatali.com/posts/xmpp-self-hosting-tutorial/) by [Fabio Natalli](https://fabionatali.com/)

s/Natalli/Natali/

you might want to mention it is for Prosody and Guix

- [XMPP self-hosting tutorial](https://fabionatali.com/posts/xmpp-self-hosting-tutorial/): how to install and configure [Prosody](https://prosody.im) on a [Hetzner](https://www.hetzner.com/) cloud instance, provisioned and configured with [Guix](https://guix.gnu.org/) and the powerful guix deploy command. By [Fabio Natali](https://fabionatali.com/)

Thank you 🙂

Hello everybody, I hope this is the right place to ask this, otherwise let me know where I can write it. I am an activist of the Italian XMPP community ( https://www.xmpp-it.net/ ) , and in these months I have mainly written the manuals part of the italian wiki, writing about xmpp clients and xmpp general notions ( https://wiki.xmpp-it.net/xmpp-it:guide:indice ) . I did this because when I started using XMPP with my community I found hard to find all the information about the various software, what are the differences, how to solve the various problems, etc... I find all the information very fragmented on the web and some simply don’t exist, but the xmpp-it MUC has helped me a lot ( xmpp:xmpp-it@conference.xmpp-it.net?join ). Anyway it took to me some months to understand many things. If I had access to a wiki like the one we have now created, I think I would have understood everything in really less time. I think many people turn away from XMPP when they encounter some seemingly insurmountable obstacles and find no answers. So at least it happened to me the first time I approached Xmpp 2 years ago, fortunately in October I've chosen to to try it again. So I would like to ask if I can contribute in the same way that I did in the Italian wiki ( https://wiki.xmpp-it.net/ ) in the xmpp.org wiki, perhaps by inserting a "Manuals" point under the actual "Quickstart" entry (of course in English), where I would implement a manual part like the one in Italian wiki. I’m not very good at English, but I think that many people could help me :) I think these Manuals could help thousands of people in the next years.. regards, Vril ✏

Hello everybody, I hope this is the right place to ask this, otherwise let me know where I can write it. I am an activist of the Italian XMPP community ( https://www.xmpp-it.net/ ) , and in these months I have mainly written the manuals part of the italian wiki, writing about xmpp clients and xmpp general notions ( https://wiki.xmpp-it.net/xmpp-it:guide:indice ) . I did this because when I started using XMPP with my community I found hard to find all the information about the various software, what are the differences, how to solve the various problems, etc... I find all the information very fragmented on the web and some simply don’t exist, but the xmpp-it MUC has helped me a lot ( xmpp:xmpp-it@conference.xmpp-it.net?join ). Anyway it took to me some months to understand many things. If I had access to a wiki like the one we have now created, I think I would have understood everything in really less time. I think many people turn away from XMPP when they encounter some seemingly insurmountable obstacles and find no answers. So at least it happened to me the first time I approached Xmpp 2 years ago, fortunately in October I've chosen to try it again. So I would like to ask if I can contribute in the same way that I did in the Italian wiki ( https://wiki.xmpp-it.net/ ) in the xmpp.org wiki, perhaps by inserting a "Manuals" point under the actual "Quickstart" entry (of course in English), where I would implement a manual part like the one in Italian wiki. I’m not very good at English, but I think that many people could help me :) I think these Manuals could help thousands of people in the next years.. regards, Vril ✏

Hello everybody, I hope this is the right place to ask this, otherwise let me know where I can write it. I am an activist of the Italian XMPP community ( https://www.xmpp-it.net/ ) , and in these months I have mainly written the manuals part of the italian wiki, writing about xmpp clients and xmpp general notions ( https://wiki.xmpp-it.net/xmpp-it:guide:indice ) . I did this because when I started using XMPP with my community I found hard to find all the information about the various software, what are the differences, how to solve the various problems, etc... I find all the information very fragmented on the web and some simply don’t exist, but the xmpp-it MUC has helped me a lot ( xmpp:xmpp-it@conference.xmpp-it.net?join ). Anyway it took to me some months to understand many things. If I had access to a wiki like the one we have now created, I think I would have understood everything in really less time. I think many people turn away from XMPP when they encounter some seemingly insurmountable obstacles and find no answers. So at least it happened to me the first time I approached Xmpp 2 years ago, fortunately in October I've chosen to try it again. So I would like to ask if I can contribute in the same way that I did in the Italian wiki ( https://wiki.xmpp-it.net/xmpp-it:guide:indice ) in the xmpp.org wiki, perhaps by inserting a "Manuals" point under the actual "Quickstart" entry (of course in English), where I would implement a manual part like the one in Italian wiki. I’m not very good at English, but I think that many people could help me :) I think these Manuals could help thousands of people in the next years.. regards, Vril ✏

vril, sounds great! Do you already have an account on the wiki?

> vril, sounds great! Do you already have an account on the wiki? 🙂️ no ↺

I will follow these steps https://wiki.xmpp.org/web/Sysops , ok?

Yup. :)

Oh, a new matrix post was linked here: https://www.reddit.com/r/linux/comments/1iv2mr3/matrixorg_bridges_to_shut_down_in_1_month_unless/ "So unless the Foundation manages to raise $100,000 of funding by the end of March 2025, we will have to focus our resources on the critical lines of work, and consequently we will have to shut down all the remaining bridges hosted by the Matrix.org Foundation. This includes bridges to Slack, XMPP, OFTC (IRC), and Snoonet (IRC). We will also mark the software behind those bridges as archived, as we don't have the resources to accept new contributions. In practice, the Foundation needs an additional $610K in revenue to break-even, but this $100K would extend our runway 1 month while we work on landing grants and new members. To put this in context, we nearly doubled our revenue in 2024, reaching $561K, but it was also the first year in which we carried the full cost of our operations: $1.2M. To make ends meet, we liquidated $283K worth of cryptocurrency donations and ended the year with a $356K deficit. We are currently on target for $587K revenue in 2025, with a modest increase in expenses."

I am not using the matrix bridge, but maybe this is important for someone in this room

I don't think many people are still using the original matrix.org hosted Bifrost instance given how broken is always was.

this has bigger impact on the remaining IRC bridges

> Oh, a new matrix post was linked here: > https://www.reddit.com/r/linux/comments/1iv2mr3/matrixorg_bridges_to_shut_down_in_1_month_unless/ > > "So unless the Foundation manages to raise $100,000 of funding by the end of March 2025, we will have to focus our resources on the critical lines of work, and consequently we will have to shut down all the remaining bridges hosted by the Matrix.org Foundation. This includes bridges to Slack, XMPP, OFTC (IRC), and Snoonet (IRC). We will also mark the software behind those bridges as archived, as we don't have the resources to accept new contributions. > > In practice, the Foundation needs an additional $610K in revenue to break-even, but this $100K would extend our runway 1 month while we work on landing grants and new members. To put this in context, we nearly doubled our revenue in 2024, reaching $561K, but it was also the first year in which we carried the full cost of our operations: $1.2M. To make ends meet, we liquidated $283K worth of cryptocurrency donations and ended the year with a $356K deficit. We are currently on target for $587K revenue in 2025, with a modest increase in expenses." Who cares of it? Are there IRC news perhaps? ↺

I think, that IRC is interesting.