edhelashopefully I don't have the JS clients limit
edhelasfinally, some good things of having a server side based XMPP client !
flowlovetox> i have a user, which host its muc service and httpupload service on the same hostname
should be perfectly fine, in fact, you should be able to run most services under the main XMPP name, which makes many things a lot easier, e.g. less dns entries, less stuff to put in the certificate (and to authenticate)
Zashflow, can I interest you in authoring a XEP saying that?
Zashcurrently some clients don't work unless you put HTTP Upload on a subdomain
Zashwhile some others don't work if you put XEP-0215 on a subdomain
ZashMUC has the thing where it occupies nodeparts@ and you'd have take care not to cause conflicts with users
flowbut that's something the service implementation has to take care of
ZashIIRC some clients had to fix problems when you did put users and MUCs at the same hostname
flowthat said, I believe MUC occupying the same "namesapce" as user JIDs is a valid reason to have an extra subdomain
flowbut http upload would be better without one
Zashflow, yes, but the examples show a subdomain, so that's what at least one client did, and thus you have to deploy it like that or it doesn't work
flowZash, did you open issues for clients which need http upload on an extra XMPP address?
Zashand they didn't want to change because look at the XEP!
flowI think I could be presuaded in writing a patch for the http upload XEP to not use an extra XMPP address if it has consensus✎
flowI think I could be persuaded in writing a patch for the http upload XEP to not use an extra XMPP address if it has consensus ✏
ZashI'm only really aware of Siskin, and that issue was closed
flowclosed as WONTFIX?
flowhttps://github.com/tigase/siskin-im/issues/37#issuecomment-625876730 is probably a hint that some tribal knowledge of XMPP got lost
flowIIRC there is a way to iterate all "services" of a user's server to discover the feature
flowe.g. that PSI does to find components
flowthat way, it should be trivial to discover that http upload is provied by the user's server address directly
MattJFWIW my preferred fix is for someone to write an informational "how to discover services" XEP
flowyes, but I wonder why this is not part of xep30 already
flownot saying that it must go int xep30, only that it feels like the right place to mention it from the beginning
MattJYeah, in hindsight it should have been I think
ZashWhat's this saying? https://xmpp.org/extensions/xep-0030.html#items-relationship
flowseems to come pretty close to it
Zashhttps://xmpp.org/extensions/xep-0045.html#disco-service seems to perpetuate the subdomain requirement
ZashThere's also the thing with node-less MUCs
lovetoxin case of gajim, it works if you put httpupload without subdomain
lovetoxwhat it seems the user did was, it put muc and httpupload on the same subdomain
lovetoxwhich was unexpected because i discover these with disco-items
lovetoxand for some reason i thought, every items belongs to one service
lovetoxso after i found a service in the subsequent disco info for the item