Modern XMPP project discussion - 2026-02-14

Is there a client yet that does server side spaces? Would like to try it out, if there's one yet.

no

> FWIW, I'm a year on with xmpp and it's my pick for messaging ecosystem but I'm actively looking for other options for org related messaging because of this gap. I currently host mattermost but looking at a migration to Zulip (coincidentally just today publicized as the destination for Mastodon's internal comms from Discord) Same for me, looking for something for my workplace. I just need to find a client that does OIDC and how to set that up on the server side. Haven't really found anything. ↺

OIDC would be the requirement.

(Perhaps another SSO method would be acceptable as well)

> But I think it's just that most of them don't make them as prominent in the UI as all the examples you mentioned With the new libadwaita Gajim I had to search for it for half an hour until I found it again, definitely not easy to find :) ↺

> In Cheogram it has a "Browse space" in the channel details, in Gajim you have to click to join a new channel and then you can see/search. But all those require more effort than Mattermost or Slack. Inteteresting. I've always used "Discovery services" for this. Now, that I haven't discovered. How and where does it search? ↺

>> In Cheogram it has a "Browse space" in the channel details, in Gajim you have to click to join a new channel and then you can see/search. But all those require more effort than Mattermost or Slack. > Inteteresting. I've always used "Discovery services" for this. Now, that I haven't discovered. How and where does it search? That's for public rooms, no? ↺

> (Perhaps another SSO method would be acceptable as well) If LDAP suffices, prosody and ejabberd have documented support, I haven't implemented yet but have plans to for prosody. ↺

And I think you know, zulip supports LDAP and OIDC https://zulip.readthedocs.io/en/stable/production/authentication-methods.html#openid-connect

until there is a client supporting it you could probably solve it on the server side. Similar to shared roster on the server side you could have a server plugin that adds all the rooms with autojoin to your users

> XEP-0503 is basically only needed if you want to host multiple "spaces" on a single domain, but I personally would argue this isn't best practice If you want to manage spaces as <rooms>@<space_name>. conference.host.tld , don't you then need to mess with DNS and Certs? I think having the capability fully self-contained in the server has a lot of appeal

That's pretty much what we've been doing for 27 years, except only one space per domain ;)

or, 24 years?

But yeah, you could do DNS and create additional conference domains instead of what that XEP talks about (I've not really read it, but I hear there's pubsub)

I mean, people want to create spaces by configuration, on the spot, having to shell out for DNS or cert management means it won't happen in the general case

> I mean, people want to create spaces by configuration, on the spot, having to shell out for DNS or cert management means it won't happen in the general case depends on how you define the personas (people). Many compare it to the Discord use case. On Discord you have many huge communities. To copy this use case spinning up a conference subdomain is the right thing to do I think. I you have you use case is a small family with ~20 users that justs needs some family rooms and does not have their own server then this is harder. Because they probably want to reuse a public server and host there their tiny space ↺

rom1dep: Wildcard DNS and wildcard certificates exist and are already in use, which makes this definitely possible