lovetoxmoparisthebest, what is now the prefered solution for websocket?
lovetoxshould i remove it completely?
lovetoxis there a use case for desktop clients?
lovetoxi originally replaced bosh with it
lovetoxbut i ask myself now if there is a situation where you would want to use websocket instead of tcp on a desktop
Link Mauvelovetox, when you have a really bad firewall on your network usually.
Link MauveOr when the server only has that configured.
debaclehas left
lovetoxthe firewall thing is stated often, but im not particular inclined to provide a software for people that circumvent their work enviroments
Link Mauvelovetox, the preferred solution for discovering WebSocket (and BOSH) endpoints is to follow the HTTP workflow of XEP-0156.
debaclehas joined
Link MauveIt’s not just work, it’s also airports, schools, universities, some cafés.
Yagizаhas left
emushas joined
Yagizаhas joined
Yagizаhas left
lovetoxLink Mauve, why you disabled websocket on jabber.fr?
Yagizаhas joined
sonnyhas left
Link MauveOh did we?
Link MauveIIRC there was an issue with some version of Converse, which started preferring it to BOSH, and I didn’t have time to investigate.
FireFlyhas left
Link MauveAt the time, BOSH was generally better than WebSocket, now that XEP-0198 can be done over WebSocket it’s probably the opposite..✎
Link MauveAt the time, BOSH was generally better than WebSocket, now that XEP-0198 can be done over WebSocket it’s probably the opposite. ✏
Link MauveDo you do 0198 in that case?
Link MauveIt would be better if this /.well-known/host-meta had a way to tell clients about preferences, but alas the web always has to reinvent SRV poorly…
FireFlyhas joined
Link MauveConverse doesn’t seem to notice websocket being blocked by CSP.
debaclehas left
lovetoxCSP?
lovetoxi mean in your hostmeta file websocket is commented out
lovetoxmeaning i have no way of testing my code :)
debaclehas joined
ZashContent-Security-Policy, a browser thing
lovetoxyes i do 0198 over websocket
lovetoxis this useless?
debaclehas left
lovetoxbecause we always know if a message reached the server?
ZashNo, 198 is good
ZashThe thing is that BOSH has equivalent functionality built in, so WS needs 198 to be comparable
antranigvhas joined
antranigvhas left
debaclehas joined
nephelehas joined
Link Mauvelovetox, it isn’t commented out any longer, but also still not working.
debaclehas left
nephelehas left
lovetoxk thanks, yeah its enough for me to retrieve the uri from somewhere
inkyhas left
Mjolnir Archonhas left
Marandahas left
Mjolnir Archonhas joined
Marandahas joined
nephelehas joined
debaclehas joined
Link MauveHeh, module:list() | grep websocket → *crickets*
alhas joined
Link MauveBut since we haven’t updated since the previous CVE, I won’t enable it today.
Link Mauvelovetox, I will comment it out again in the host-meta, unless you want to continue debugging.
Link MauveI will uncomment it once we are ready to reboot the server for upgrades.
lovetoxhm would be cool if you could leave it until tomorrow
lovetoxim just finishing the code
Link MauveThat prevents our web users from being able to connect at all. :/
Link MauveCouldn’t you pick any of the other correctly-configured servers here? https://compliance.conversations.im/test/xep0156/
nephelehas left
marchas left
marchas joined
debaclehas left
alhas left
lovetoxno, your users can wait till tomorrow
lovetox:) of course then comment it out, i take another server
goffihas left
Laurahas left
Laurahas joined
sonnyhas joined
miruxhas left
miruxhas joined
dezanthas left
larmahas joined
nephelehas joined
nephelehas left
nephelehas joined
nephelehas left
antranigvhas joined
abdullahhas joined
antranigvhas left
PapaTutuWawahas left
abdullahhas left
kfvhas left
kfvhas joined
abdullahhas joined
antranigvhas joined
oxtypedhas joined
PapaTutuWawahas joined
dezanthas joined
goffihas joined
inkyhas joined
moparisthebestlovetox: websocket is valuable, just needs looked up via host-meta, and I'd probably suggest standardizing on host-meta json, it's in the RFC
moparisthebestIn fact I'm going to propose an update to '156 saying that...
mhhas left
mhhas joined
goffihas left
larmahas left
oxtypedhas left
oxtypedhas joined
debaclehas joined
oxtypedhas left
Martinhas left
nephelehas joined
rafasaurushas left
rafasaurushas joined
Martinhas joined
pasdesushihas left
stuart.j.mackintoshhas left
stuart.j.mackintoshhas joined
debaclehas left
nephelehas left
spectrumhas left
miruxhas left
debaclehas joined
miruxhas joined
spectrumhas joined
pasdesushihas joined
xeckshas left
nephelehas joined
xeckshas joined
nephelehas left
oxtypedhas joined
oxtypedhas left
lovetoxbut thats to late
lovetoxnow everyone implemented updated it and probably everybody uses whats in the xep the xml
larmahas joined
lovetoxjust leave it at that
lovetoxas this are xmpp clients, all software deals with xml anyway
lovetoxi dont even know why there is a second solution here
alhas joined
oxtypedhas joined
moparisthebestlovetox: because it's in the host-meta RFC
lovetox?
moparisthebestAnd all XMPP clients should be doing posh anyway which is json only
lovetoxand its also in the XEp
lovetoxwhy do you need to standardize on json
moparisthebestThe json representation is in the host-meta RFC too I mean
lovetoxok you mean thats why its in the XEP
moparisthebestIt makes sense to standardize on one instead of always grab both
lovetoxbut it does not explain why you want to remove the xml represantation
Link Mauvemoparisthebest, no need to fetch both, as the XRD version is required to be present.
lovetoxmoparisthebest, we dont need to grab both, because one is optional and the other not currently
moparisthebestAnd fun fact: the example XML in the host-meta RFC is invalid according to the XRD spec, it doesn't validate
lovetoxif you change this now, THEN we definitly need to grab both
moparisthebestYou already have to grab both, I'd like to strongly recommend only grabbing the json
lovetoxno
lovetoxjson is optional
moparisthebestAlso the XRD spec website has a "always valid look to the latest xsd" that returns 404 lol✎
moparisthebestAlso the XRD spec website has a "always valid link to the latest xsd" that returns 404 lol ✏