XMPP Service Operators - 2022-12-25


  1. abdullah

    Happy Christmas happy holidays to everyone.

  2. Trung

    😊 Merry Xmas abdullah

  3. coleman

    Same to you all

  4. reload

    Merry xmas everybody! We are setting up an xmpp Server and have a few questions. Maybe somebody is willing to answer

  5. reload

    Can xmpp be handled over http(s) only? I.e. connections via subdomains on 443 instead of 5223/5270 Is there a backend which can handle xmpp on a single port but instead use a load-balance or reverse proxy of web socket to accomplish the multiple port use What xmpp clients work best for connecting to an xmpp that is a hidden service only

  6. Peter Waher

    Merry Christmas

  7. Peter Waher

    On first question: You can use BOSH (XMPP over HTTP) or Websockets to connect to the XMPP network as well

  8. Peter Waher

    References: * XEP-0124 * XEP-0206 * RFC-7395

  9. moparisthebest

    reload: do you want it to federate with the rest of the XMPP network or not

  10. Licaon_Kter

    reload: XEP-368 multiplexing over sslh or nginx

  11. Licaon_Kter

    reload: hidden servico means .onion?

  12. Licaon_Kter

    reload: hidden service means .onion?

  13. reload

    > reload: do you want it to federate with the rest of the XMPP network or not Federate is ideally yes

  14. reload

    > reload: XEP-368 multiplexing over sslh or nginx I’m more familiar with Nginx

  15. reload

    > reload: hidden service means .onion? Yes

  16. moparisthebest

    reload: so you can accept all incoming connections on one port no problem, if that port can only do http that will severely limit the clients that can be used to only those that can do WebSocket, and in practice cut you off from federating with public servers because only 1 currently can do s2s over WebSocket

  17. moparisthebest

    Also very few servers can successfully federate with .onion domains

  18. Licaon_Kter

    reload: .onion does not need http or multiplexing or anything

  19. Licaon_Kter

    > Also very few servers can successfully federate with .onion domains This too, yes

  20. reload

    > reload: so you can accept all incoming connections on one port no problem, if that port can only do http that will severely limit the clients that can be used to only those that can do WebSocket, and in practice cut you off from federating with public servers because only 1 currently can do s2s over WebSocket Satori Hoshi: Websocket then I just mean http assuming I am running on 443 Can still be websocket at that port

  21. reload

    > reload: so you can accept all incoming connections on one port no problem, if that port can only do http that will severely limit the clients that can be used to only those that can do WebSocket, and in practice cut you off from federating with public servers because only 1 currently can do s2s over WebSocket Websocket then I just mean http assuming I am running on 443 Can still be websocket at that port

  22. reload

    Also. I don’t mind subdomains. My big question is what backend is best to do the summary of these

  23. Licaon_Kter

    Multiplexing means that the connection to that one single port is forwarded to xmpp or http or whatever, so it appear you only have 443 but...several services live behind it

  24. reload

    Getting clients to connect to non-traditional methods is the main issue

  25. Licaon_Kter

    Backend? Summary?

  26. moparisthebest

    But what I'm saying is you can run regular XMPP on port 443 too, not just https, then you'll be able to federate with the whole public network (just add srv records so they know what port to use)

  27. Licaon_Kter

    reload: SRV settings in your DNS are respected by most clients so they'll connect to 443 or whatever you put there

  28. moparisthebest

    Clients will use SRV records as well

  29. reload

    > Multiplexing means that the connection to that one single port is forwarded to xmpp or http or whatever, so it appear you only have 443 but...several services live behind it Perfect!

  30. reload

    > Backend? Summary? Ejabberd, prosody or open fire? What will work best for this?

  31. reload

    And a client for connection via hidden service Built in tor proxy

  32. Trung

    😊 i say Prosŏdy, Licaon_Kter gonna say Ejabberd, i don't know what that moparisthebest guy is gonna say

  33. Licaon_Kter

    reload: > Ejabberd, prosody or open fire? What will work best for this? All work I use ejabberd, others use prosody Read about Snikket too

  34. moparisthebest

    reload: this is an example of how I host multiple services behind port 443, I use sslh myself https://wiki.xmpp.org/web/Tech_pages/XEP-0368, any XMPP server should work fine for that, I use prosody

  35. Sapotaceae

    prosody is the only one that can easily do s2s to other onions afaik

  36. Licaon_Kter

    reload: > And a client for connection via hidden service > Built in tor proxy Not included, no Dino Gajim Conversations All can use .onion and normal Not sure on iOS/mac

  37. reload

    Sorry it is mostly that there is a lot of people doing a lot of things. The ideal tools for the ideal application

  38. Licaon_Kter

    Sapotaceae: > prosody is the only one that can easily do s2s to other onions afaik mod_dark or mod_onion or something, yes

  39. reload

    > reload: this is an example of how I host multiple services behind port 443, I use sslh myself https://wiki.xmpp.org/web/Tech_pages/XEP-0368, any XMPP server should work fine for that, I use prosody Amazing. Thanks

  40. Licaon_Kter

    > The ideal tools for the ideal application Funny, you won't have this here, they're all ideal :))

  41. reload

    Nice to hear :))

  42. reload

    Thanks all. We will send a welcome as soon as it is setup :)