This blog post was originally a wall of text on GNOME’s Discourse to involve the GNOME Project community in the shaping of the GNOME Foundation’s programmes.
The GNOME Foundation has not been giving as much news as we wish it has, but doesn’t mean nothing happened!
I self-host a few services. It’s easy to put services online, but self-hosting properly in the long run is difficult. A part of self-hosting properly is having backups and monitoring. In this article I’m going to show you how I make sure to get off-site backups, with a Raspberry Pi at home pulling data from my VPS. There’s room for improvement, and if you have constructive comments on how I can do better I’d be happy to hear them!
The threat I’m working against is data loss. It can happen because my VPS gets hacked, in which case I want to destroy the VPS to prevent it from bein exploited further without having to think twice. If my data is leaked, I don’t want the additional burden of not having access to it myself
When we deployed our Matrix instance for GNOME, we were really used to IRC. We did not think through all the ways people would use an account for, and left registrations too open. As a consequence, many people created an account on our instance because they like the GNOME Project, and started using it as a personal account.
Now that we are more experienced with the difference between an organisational account and a personal one, I would like to walk you through the differences between the two, why segregating activities can be useful, and finally how to migrate data from an account to another.
This post follows an introduction to Matrix with e-mails, where I explain that Matrix is a federated system.
Federation can be either public or private. A public server can communicate with any other server, except the ones which are explicitely avoided. Meanwhile, a private server can only communicate with a selected list of other servers.
