Hmm, seems like I’ve convinced myself to stick with it for now, and we’ll see how it goes. I could also hold out for Dendrite or Conduit to mature enough that I’m ready to try them, which might not be more than a few months off. That still leaves me with the question of whether I’m comfortable running a service that others may come to rely on, or being responsible for the safety of their information. I wouldn’t ever want to make it a paid-for service but perhaps people might be willing to make occasional donations towards running costs. So I could start opening up for other users, and at least justify the size of the server that way. Neither are quite ready for what I want yet, but are getting close, and when ready that will allow running small homeservers with much more sensible resource usage. Secondly, there are a couple of alternative server implementations in development specifically addressing this issue for small servers. So if users have mostly overlapping interests, and thus keep to the same rooms, you can support quite a large community without significant extra resource usage. Firstly, Synapse resource usage is entirely down to the size of the rooms joined by users of the homeowner, not directly the number of users. There are a couple of other considerations here. So now I have to make a decision about whether it’s worth keeping going, or shutting it down and going back to, or setting up on one of the other servers that have sprung up in the last couple of years. Synapse, the only full server implementation at the moment, is really heavy on memory, so I’ve ended up running it on a much bigger server than I thought I’d need, which seems overkill for a single-user instance. My problem now is whether to keep self-hosting. So, I really like Matrix and I use it daily. I’ve also found that my use of Matrix-only rooms has grown as more individuals & communities have adopted the platform. Since then, I’ve also added a fourth goal: taking advantage of various bridges to bring other messaging network I use (such as Signal and Telegram) into a consistent UI. Thirdly, to take some control of the loss of access to historical messages in some communities that rely on Slack (especially the Carpentries and RSE communities). Secondly, to try and rationalise the Cambrian explosion of Slack teams I was being added to in 2019. Firstly, to see if I could and to learn from it. I decided to host my own for three reasons. Federated in that, like email, it doesn’t matter what server you sign up with, you can talk to users on your own or any other server. Open in that the standard is available for anyone to view, but also the reference implementations of server and client are open source, along with many other clients and a couple of nascent alternative servers. Matrix is something rather cool, a chat system similar to IRC or Slack, but open and federated. NB! Pantalaimon is not a user-facing client but a locally running proxy for other clients, to handle E2EE on their behalf.I started running my own Matrix server a little while ago. Weechat-matrix ( upstream) - since bullseye Dendrite is a second-generation Matrix homeserver written in Go. Purple-matrix ( upstream) - ROM unmaintained Pantalaimon ( upstream) - since bullseye orphaned Matrix-mirage ( upstream) ROM Orphaned, possibly dead upstream, dependency qtav is dead upstream Matrix-hydrogen ( upstream) - only in experimental orphaned Just have in mind the specifics of our team (another group on Salsa, another mailing list, etc.). All rules about level of access, creation of git repositories and such like are similar in both teams. You may find some useful information about using of Salsa for packaging of software in the Debian Science Policy Manual. If you are subscribed to Planet Debian you will see them there. Some useful notes will be on in official blog. Packaging team uses Salsa with a mailing list.ĭiscussion about Matrix packaging takes place in #debian-matrix: ( logs older logs). To discuss Debian using Matrix see the Debian space #debian-space. Please feel free to package any of the software listed on this page that hasn't already been packaged or ITPed! This page lists Matrix-related software, and their status in Debian.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |