Modern XMPP project discussion - 2025-01-03


  1. arcanicanis

    Out of curiosity, are there any server or client projects currently implementing GC3, or just the text of the XEP still being drafted first?

  2. arcanicanis

    Out of curiosity, are there any server or client projects currently implementing GC3, or just the text and logic of the XEP still being drafted first?

  3. Kris

    GC3 is afaik a remix and standardisation of existing MUC modules, so Prosody at least should have it mostly covered already.

  4. arcanicanis

    Well, didn't know that was a UX thing in Conversations: if you add a contact where the domain-part of the JID is to the pattern of "chat.(domain)", it warns that "This looks like a channel address"

  5. arcanicanis

    Maybe there should be a list of recommended user-friendly subdomains to use for the main domain (used for accounts), if a person doesn't want to (or can't) use their plain domain)

  6. arcanicanis

    Maybe there should be a list of recommended user-friendly subdomains to use for the main domain (used for accounts), if a person doesn't want to (or can't) use their plain domain) to avoid the confusion

  7. arcanicanis

    Or have there been any advancements with delegating to a server identified by a subdomain, from the plain domain name (e.g. have users identified as *@example.com, while the actual server is xmpp.example.com, and only has a cert for xmpp.example.com and other XMPP-related services; without needing example.com in the cert)?

  8. Kris

    Yes that works fine via SRV records

  9. Kris

    Just make a wildcard cert 🤷‍♂️

  10. arcanicanis

    Didn't know it worked fine from SRV records, thought there was more things involved. And yes, I have wildcard certs set up for a few servers.

  11. Link Mauve

    arcanicanis, chat. is a common prefix for user domains as well, maybe your client should do a service discovery instead to be certain that a particular domain is for users or for channels/groups.