Because the XEP is not for me. My goal is to let xmpp(.js) users say this is the service (as domain) I want to connect to - I don't care how just establish an XMPP connection there.
It's working fine unless the only transport available is WebSocket (not uncommon with xmpp.js) and the instance is private which is usually where first time users get started. The alternative I have considered is adding to the documentation the default WebSocket URL for each known XMPP server. Not sure about bosh - xmpp.js does not support bosh as it seems irrelevant with WebSocket and there was no interest for it. Perhaps bosh "recommended" endpoints should be added as well. -- Sonny Piers [email protected] On Wed, Feb 3, 2021, at 18:43, Sam Whited wrote: > In that case, why have an XEP at all? If you're doing anything like > this you don't need the defaults to be standardized across services to > aid in interop, you just know what your servers default is and can just > connect to it. > > —Sam > > On Wed, Feb 3, 2021, at 12:29, Sonny Piers wrote: > > I agree with the points raised, but I suggest we forget about public > > deployments, looks like the only valid use case for this proposal is > > to have default endpoints for non-public facing services (CI, > > localhost, development, ...) > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ > _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
