

There is a better, community maintained fork now: https://github.com/matterbridge-org/matterbridge
Admin on the slrpnk.net Lemmy instance.
He/Him or what ever you feel like.
XMPP: povoq@slrpnk.net
Avatar is an image of a baby octopus.


There is a better, community maintained fork now: https://github.com/matterbridge-org/matterbridge


https://hypersomnia.io/ can be played in the browser and probably also selfhosted.


The XMPP channel search has a few channels that are not assorted geekery, but yeah most of it is.


Snikket is definitly not harder to set up than Synapse or Condinuwuity, the difference is mainly that Matrix is based on standard web technology, so if you have some knowledge in that already, XMPP can feel a bit alien since it is an actual protocol different from http(s).


Snikket makes it quite easy, but the extra complexity of hosting from home is probably better avoided for total beginners.


Yes, Matrix is a bit ahead with SFU calls (after depending on Jitsi Meet for a long time, which uses xmpp under the hood). But for most usecases it doesn’t matter so much. On a modern internet connection a SFU basically only starts being useful in calls with ten or more participants. For corporate board meeting calls maybe, but your family call is also fine without.


For now voice and video calls in xmpp only lightly touch the server and are mostly p2p. This comes with some scaling issues but for small groups of around 5 people it works fine.
Movim is a bit special, for other clients it doesn’t matter much.


Movim specifically works a bit better with ejabberd, who also provide easy to use containers.
Prosody is more of a Lego set to build your own server, so I don’t think they even provided official container images for a long time. There is https://snikket.org/ though which is an opinionated distribution of Prosody with easy to use containers. Sadly Snikket doesn’t play so well with Movim out of the box.
In general it is probably easier to start out with a rented VPS. You can move to your own server later on when you got the basics down. Since XMPP servers are quite lightweight they run fine on low end VPS that can be rented for as little as 1€/month.
At some point the benefit of extra RAM isn’t there anymore compared to what the CPU can actually run. With a CPU like that 8GB is probably sufficient and 16 would be merely nice to have for some additional caching.
I would go for the Wyse 5070 as a server. More RAM is good and the CPUs while somewhat slower are more power efficient.
The 4/5th gen Intel CPUs are the last gen that is really quite poor in power efficiency when mostly idling. 6/7gen made huge improvements in that regard.
Upgrading the storage should be possible quite easily.


For static sites, yes. To actually protect dynamic sites against AI crawlers, Cloudflare has to do much more than just caching.
And besides that, Cloudflare is a huge single point of failure and highly privacy invasive.


This will just make them sound more believable when they hallucinate. LLMs can conceptually not be made to not lie, even if all the info they are trained on is 100% accurate.


This is not how things work on the modern web. Did you just wake up from a 20 year coma?
https://f-droid.org/packages/se.lublin.mumla is not so bad as a mobile client for Mumble.


It’s a fork of a fork or Conduit.


Starting point based on what? Do you plan to use it personally to join many large channels from FOSS projects? If so, you need to plan for a relativrly beefy VPS, like 4 core, 8gb ram, 100gb+ ssd storage.
But for small private chats with no federation a cheap minimum VPS can work.
If you want my personal recommendation I would avoid hosting Matrix. A well federated server is costly to run and not really worth the hassle and a small private chat server with bridges etc can be done equally well or better with XMPP.


As others have already alluded to, Matrix is a bit odd in that regard as it runs a distributed database and the resource requirements depend on how much of the matrix network is mirrored on it. A single power-user can cause huge resource use just by connecting to a lot of federated active rooms. On the other hand a server that is mostly used as a private family chat can run on a modern RasberryPI without much problems.
Synapse or Conduwinity etc. makes little difference in praxis as both need to do the same database merging operations.
That must have been a severly misconfigured server then. Normally history is stored on the server and synced on demand via MAM.
Of course with modern e2ee you can’t actually decrypt old history on new devices, but that is an intentional feature with PFS.
Xmpp has no marketing budget and a lot of people just decided it is old and always share bad experiences with it from 15 years ago 🤷
Ghost in the machine 🤷
Impossible to tell and it sometimes happens.