XSF Discussion - 2023-08-04

I will open and communicate to collect all out information today

where do I report bugs and/or ask questions about connect.xmpp.net

(I'm guessing that's a question for jonas’ )

The frontend, me, the backend, jonas’

uh, probably backend, Server-to-server connectivity both said "Connected" even though Direct TLS was broken

actually prosody using people could join the MUC but ejabberd folk could not, it's a seperate bug I'll need to report to them :D

but I fixed my server so either need a badxmpp for this or I can set up another broken one

moparisthebest, broken in which way exactly?

well it connected to a web server that didn't speak XMPP at all

the only difference in the output was it didn't say "SASL mechanisms: EXTERNAL"

hm

that's sad

myeah, reproduces when using xmpp:https.badxmpp.eu as a test case

http or https.badxmpp.eu

quite sad indeed

moparisthebest, I filed https://github.com/horazont/xmpp-blackbox-exporter/issues/24 for tracking, not super inclined to work on this right now

the ejabberd bug is it doesn't proceed to other SRV records, just "remote timeout"

thanks jonas’ , just wanted to get it written down somewhere

oh no, new prosody has the same bug as ejabberd

gonna have to set up another broken testcase

Not moving on srv records? I think I encountered that once

Yep

Wait do we have Direct TLS s2s in a release already?

Oh, I thought that was trunk only still.

But Happy Eyeballs aren't in a Prosody just yet, which does a lot for avoiding all those serial per-connection timeouts adding up to the point where it gives up on the whole s2s attempt.