Modern XMPP project discussion - 2025-04-22

Is it even a lot of stuff?

The three things are pretty straightforward but yeah

What three things?

In Link Mauve's messages above. Numbered: 1) Some just forget to publish AAAA records, 2) some do but forget to make their server listen on INET6, 3) Some forget to configure their firewall to allow IPv6 traffic to those ports

I've tried deleting my default route for IPv4 for a couple minutes and suddenly the same amount of connections was there for IPv6 as it has been before in total:

https://share.erebion.eu:5281/file_share/SWlA09iq_JWP8nkWN9uXaxUv/b83a0c0e-6a1f-4606-a599-ef559a24b797.png

This is before deleting the default route:

https://share.erebion.eu:5281/file_share/p6gSSjaWGQ4wc9tTL8bNDgHo/cedf15c4-0994-4dcc-a8a8-66b0cfc882d6.png

So it seems Prosody sometimes connects via IPv4 while it could use IPv6 ✏

It could happen if your IPv6 routes have more latency

Hmm, or maybe we're missing the recommended AAAA delay, I can't see it in the code right now

it's in net.connect, 250ms

Hmm, are you sure that's the one?

The RFC says 50ms

The new one?

Mmm, yeah, I was reading the new one

Wait "resolution delay" ?

But AFAICT the delay in net.connect is between "basic" targets

the "Connection Attempt Delay" I guess

I don't see anything that gives AAAA a headstart

net.resolvers.basic seems to fire the DNS queries in probably a random order

Oh no

Maybe the state of IPv6 in XMPP isn't as depressing as we thought

AFAIK we do A and AAAA (and TLSA) queries at the same time, wait for all to finish, sort them in some way that puts an AAAA first, try to connect to that and then 250ms later try the next

Maybe it's just because Prosody doesn't prefer IPv6 per whatever the Happy Eyeballs RFC is xD

Ah yeah, just noticed merge_targets()

Huh, but why does it use IPv4 while it can use IPv6?

When I deleted the default route and added it back, it started using more IPv6

Networks work in mysterious ways.

Could it be that my DNS just had issues exactly at the time when I looked at the data yesterday?

Also, found those hosts without AAAA records: conference.debian.org: conference.debian.org has no AAAA record conversations.im: conversations.im has no AAAA record disroot.org: disroot.org has no AAAA record muc.xmpp.org: muc.xmpp.org has no AAAA record

Those are all the servers in my log that don't allow IPv6.

Does anyone here have contact to one of the admins and could ask them to that pls? :)

xmpp-server xmpp.xmpp.org. 9269 Priority: 1 Weight: 1 IP: 2604:a880:800:c1::2a:a001 IP: 104.248.10.4

Yes, but not muc.xmpp.org

muc.xmpp.org has a SRV record which points to xmpp.xmpp.org

Oh right, forgot to look for that

Guess that means time to sleep

that was the output from `xmpp-dns muc.xmpp.org`

Sounds like a good idea. Good night! o/

TIL: xmpp-dns

of course, things may fail to look up the SRV record for some reason and fall back to A/AAAA lookup with the default port

> Networks work in mysterious ways. 💯 ↺

Just a thought... What if instead of having a profile pic that is either always available or only available to contacts we had separate pics for always and contacts, so that one could have pic visible in every chat, but also one with, for example a face, visible to contacts?

*Just had a thought

Like this in a client: Profile picture Contacts: 123.jpg Everyone else: 456.jpg