Jitsi Meet with ejabberd viable in 2024? Who is running this combo successfully? #4239
-
Hi, I can only find old information on running Jitsi Meet with ejabberd... Some blog posts, like: And I noticed @weiss, @licaon-kter actively pursuing support a few years back (both here and at jitsi), e.g. This could mean that Jitsi + ejabberd has been running fine for some people (perhaps with some limitations accepted for their usage). Or people like @jirkanov have given up and lost interest... Hence my questions in the subject that's hopefully good info to have available for others: Is "Jitsi Meet with ejabberd viable in 2024? Who is running this combo successfully?" If you are, any limitations/risks/regrets I need to be aware of? TIA! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
There was this wave back in 2020, but more apps added at least 1:1 calls (and the whole reason for remote work went away ahem) In my case I just given up, it was a pain to even build for arm64. Jitsi Meet didn't care about being part of the XMPP community, having the startup mentality, pushing for more custom LUA modules and REST APIs, not XMPP interoperability. If I'd deploy now I'd just setup a prosody along side. But I'm interested to know too, if that's not needed. |
Beta Was this translation helpful? Give feedback.
-
Same here. For some newer Jitsi Meet features, you need non-standard Prosody plugins written by the Jitsi people, and I have no plans to port those to ejabberd. |
Beta Was this translation helpful? Give feedback.
Same here. For some newer Jitsi Meet features, you need non-standard Prosody plugins written by the Jitsi people, and I have no plans to port those to ejabberd.