XMPP Service Operators - 2026-05-10

~without going and looking it up, because I can just quit being lazy and do that myself instead of making someone else do it.... but if you know off the top of your head, what client apps wouldn't be able to connect if I require SASL2?~ nvm... it's all the ones I use 💀 also most of them ✏

>> Hm. I could add a ygg AAAA record and use an srv record to point to that record for s2s. > > Yes I do this Certwatch still complains about my Yggdrasil IP address, though. ↺

really? Hmm. It doesn't complain about mine...

>> yup. "Best Practices" XEPs are the unsung heroes. I think I've got the server about as China-ready as it's going to get at this point, I'll likely set up I2P as a fallback too. All that's really left is to get the Chinese homie plugged in and see what happens 🤷‍♂️ > wish tor/i2p/ygg federation were set up by more servers. more decentralization and being able to host behing cgnat I used to have s2s over tor setup for some connections for queer spark. However, last I checked, mod_onions is unmaintained and does not work correctly with the current version of prosody ↺

> without going and looking it up, because I can just quit being lazy and do that myself instead of making someone else do it.... but if you know off the top of your head, what client apps wouldn't be able to connect if I require SASL2? Dino versions older than 2 weeks ago ↺

>> wish tor/i2p/ygg federation were set up by more servers. more decentralization and being able to host behing cgnat > > I used to have s2s over tor setup for some connections for queer spark. However, last I checked, mod_onions is unmaintained and does not work correctly with the current version of prosody True, it gives an error related to some method not existing anymore. I slightly modified it to work with recent prosody and work with i2p too. Still not production ready though, there are some insecure workarounds I used when testing. ↺

> really? Hmm. It doesn't complain about mine... Yeah, I keep getting messages like > Error checking freespoken.nz: socks connect tcp localhost:9050->[201:70e:bb4f:1081:d315:ad23:ce25:5758]:5222: read tcp 127.0.0.1:42544->127.0.0.1:9050: i/o timeout ↺

But people with Yggdrasil-only setups on the other side of the world report being able to federate with me, so I'm pretty confident it's working.

>> really? Hmm. It doesn't complain about mine... > > Yeah, I keep getting messages like >> Error checking freespoken.nz: socks connect tcp localhost:9050->[201:70e:bb4f:1081:d315:ad23:ce25:5758]:5222: read tcp 127.0.0.1:42544->127.0.0.1:9050: i/o timeout I think it's an ipv6 issue. I went back to hosting on ipv4 only (was a massive headache in general) and started getting valid checks back immediately ↺

I usually don't get errors for my non-Yggdrasil IPv6 addresses.

I'll have to double check my ygg special case