XSF Discussion - 2016-01-12

FOSDEM has a lightning talk on "Ralph".

As long as he isn't struck by it...

Kev, intosi: MattJ told me you were responsible for prosody @jabber.org… hermes2v6.jabber.org (from SRV record) is not responding, and xmpp.net says your TLS config could need some love: https://xmpp.net/result.php?domain=jabber.org&type=server

I never mentioned Prosody :)

jabber.org doesn't run Prosody

did you mean "responsible for jabber.org @prosody (the room)"

And as sevral people mentioned, hermes2v6.jabber.org seems to be responding?

MattJ: sorry, I think I read that on the website

Zash: I meant "responsible for the xmpp server jabber.org"

azrael: Do you mean not responding, or you can't route to it?

hermes2v6 seems to be v6 only, that's why *I* cannot route to it

dunno about xmpp.net

That’s pretty much in the name. :)

Link Mauve: tbh, my first association was about some weird naming scheme indicating when servers have been set up or sth

well, now xmpp.net doesn't complain anymore

sorry for bugging you with that … but the TLS config is still the same

hermes2v6 responds nicely over ipv6, just a bit slow because it resides on the other side of the pond...

hermes2v6 responds as expected, xmpp.net doesn't seem to like an IPv6-only connection.

It answers at a surprisingly stable 140ms ping.

From France.

same here, xmpp.net seams to be perfectly reachable over ipv6

I don't have IPv6 here, so I've never implemented it for xmpp.net (though I also don't know what exactly would need to be implemented).

Fix verse probably

it seems to work without problems over ipv6

The website?

yes

But the test system

Hmm, wget doesn’t like its certificate, although Firefox has no issue with it.

\o hexa-

ohai

Zash: testing myself now, but I don't see any xmpp.net at all in my netstat

ah... wrong port...

why IP6 should be implemented?

Test runs over ipv6