Converse.js VS dendrite

ConverseJS is a popular Javascript XMPP client that implements a full range of XMPP extensions. Also available as a plugin for openfire — inverse-openfire-plugin and can be installed on openfire with a few clicks.

I agree. IMHO the best variant is then to use something that is truely free. Like XMPP. There are a lot of servers and many clients to chose from and I can strongly recommend converse.js as a web client. It supports different ways of end to end encryption but I would recommend OMEMO which is basically the same encryption idea that you find in Signal.

Hello, I recently started exploring xmpp, with snikket app and conversejs.org

It is Converse.js (https://conversejs.org/) packaged into a one-click install for openfire (from the web admin). So, one-click install for an xmpp web client.

My choice, because it's the stack I know very well, would be Prosody ( https://prosody.im/ - I'm one of the devs) and a web client such as Converse.js ( https://conversejs.org/ ). XMPP is highly extensible, Prosody is highly modular, which make them a good foundation for building on top of.

That said, the right stack is generally the one that matches your requirements, and (if this isn't primarily a learning exercise) whatever you're most familiar with. The hardest part of building a Discord or Slack-like in 2022 is actually not the technical stuff. There are many comprehensive open-source products already out there that compete with these companies, such as Mattermost, RocketChat and Element.

Tried to register with conversejs.org today and got an error "your IP is not whitelisted".

Maybe you are remembering this bug from some months ago? It appeared exactly as if this was (accidentally) uploading keys to the user's XMPP server (not Converse.js's server) and publishing them.

Matrix already has key-based identity in the works at https://github.com/matrix-org/matrix-spec-proposals/blob/keg... (and implemented in Dendrite at https://github.com/matrix-org/dendrite/pulls?q=is%3Apr+is%3A...). Matrix is set up to let folks go wild and change fundamentals like this; basically every Matrix Spec Change (MSC) is a small fork, which then gets merged into the main spec if it can be proven to work well in the wild.

I really hope that Dendrite is getting more traction and maybe there's an OIDC solution for Matrix one day.

Yes there is an official helm chart. https://github.com/matrix-org/dendrite/releases/tag/helm-dendrite-0.11.2

This is what the Matrix team is developing Dendrite for. To have a feature-complete yet small server software. But it's still in beta.

Pinecone, which is an experimental overlay routing protocol used by P2P Matrix. It and Dendrite are extremely important to P2P Matrix.

So I want to setup an instance of Dendrite, a matrix home server. I have a docker-compose set, the yaml file in the correct directory, but I do not understand how to generate the key files. the dockerhub states that I should use this:

Dendrite, meanwhile, can be found here. They say it's in beta. I think it's a late Alpha. Dendrite's primary mode is "Monolith"; this will have many of the same scalability/balancing options that Synapse does. However the true benefit to Dendrite as I see it is the "polylith" mode where workers can swap around which worker is the master without any interruption of service. I do not think that Dendrite polylith works yet, but I might be wrong. I'll be looking at running it on a test server in January to see if it's time to upgrade from Synapse (and time to invest in 4-6 SBCs to keep three here and send 3 to 3 of my buddies to make my Matrix even more reliable).