4 ms·
And I thought that XMPP felt broken...
by ekjhgkejhgk 11mo ago
And I thought that XMPP felt broken...
- a3w 11mo agoNow you can feel twice as broken. That is what new, modern standards deliver. Is this part of XCD #927 or another one, too?
- ekjhgkejhgk 11mo agoXMPP is 26 years old, Matrix is 11 years old.
- Jnr 11mo agoXMPP felt great when compared to Matrix. Matrix was in a bad state some years ago when I hosted it for a while, and seems like it still is the same messy state. I avoid it as much as possible but for some reason there are communities using it. At this point it should just die so people would be motivated to replace it with something better.
- tcfhgj 11mo agoPeople are motivated to replace it with something better, it's called Matrix 2.0.
- Orygin 11mo agoDo they plan to fix the fundamental issues of Matrix in 2.0 or should I wait for 3.0?
- Jnr 11mo agoI tried it a year ago when it was introduced, it did not work. Is it stable now?
- this_user 11mo agoWhich perfectly fits the Matrix ethos of everything constantly being rewritten or replaced with something new that only implements half the features before the original thing is ever finished.
- bigstrat2003 11mo ago> I avoid it as much as possible but for some reason there are communities using it. The "for some reason", at least for my group, is because it's rock solid for us. We have no reason to want to change, so of course we are using it.
- aidenn0 11mo agoI've had only one issue with ejabberd (didn't read the docs close enough and had to move from mnesia to sql when I hit the size limit) in over a decade of self-hosting it. Knowing which XEPs you actually want is a bit of a pain, but has gotten easier. Now I usually just periodically look at the current prosody example[1] which lists extensions by "essential" "recommended" "nice to have" and "other" and it's easy enough to find the matching modules for ejabberd. 1: https://prosody.im/doc/example_config https://prosody.im/doc/example_config
- MattJ100 11mo agoProsody dev here. Good to know this is useful :) One of my favourite small features we added in the latest release is a 'prosodyctl check features' command which will validate that your configuration is up to date with current best practices in various ways. Although we like to curate the default configuration with care, people tend to keep their existing configuration file when they upgrade (we generally recommend this, as we aim for backwards compatibility). The new command makes it easier for folk who upgrade to ensure they are still getting the expected experience as the recommendations evolve. Obviously that has to be somewhat opinionated. One thing many people appreciate about Prosody is that you can customize it however you want to, even if it's not following the mainstream. E.g. if you really don't care about synchronizing to multiple devices, you can totally disable that message cache. Don't need audio/video calls? Fine!