XMPP Service Operators - 2025-01-10

roughnecks: it looks up now

yeah 👍

yeah ... ISP been having one of those dyas in which let us offline for a few long hours.

is cyberdelia seld-hosted at home?

> is cyberdelia seld-hosted at home? yeap ↺

As I'm planning to use it as a conversation piece at the stand of FOSDEM again (to show off the size of the public XMPP network), I'd love for you all to add your XMPP servers to https://xmppnetwork.goodbytes.im - It is a website that shows a network graph of XMPP domains.

> As I'm planning to use it as a conversation piece at the stand of FOSDEM again (to show off the size of the public XMPP network), I'd love for you all to add your XMPP servers to https://xmppnetwork.goodbytes.im - It is a website that shows a network graph of XMPP domains. 👍 ↺

That required some contrib module for ejabberd, right?

Kris: correct (that module got updated a few minutes ago, so even if you are already using it, you may want to update it). There are also modules for Tigase, Prosody and Openfire available.

(Tigase supports it without modules, but through a config change I think)

Hmm, I might look into that tonight.

Nice. Feel free to join xmpp:xmppnetworkgraph@conference.igniterealtime.org?join if you run into issues.

Guus, what do you think… How much fire would come out of that thing if we added search.jabber.network?

I'm happy to try.

My bet is that we're overrunning stanza size limits

eek

which would likely be a first for me :)

not for us unfortunately (:

is there a step-by-step guide for how to onboard a prosody server?

You'd only get a stream error on the data that you try to send.

Install https://modules.prosody.im/mod_pubsub_serverinfo.html and install the module mentioned in the 'known issue' that's documented. Ensure that your pubsub service is advertised in DNS records and is covered by your TLS certificate. That's about it, I think.

Does the known issue also affect trunk?

(and which specific versions of trunk. we're not on 0.12)

I do not know. You'd have to ask Prosody developers.

I see.

what is the layout of the data in the pubsub node? Is it one huge item, or one item per peer domain?

One huge item.

I see.

how much work would it be for you to change that to one item per peer domain?

because we will definitely hit some limits, even if not stanza size, it'd probably kill the I/O performance of the server if we wrote such a huge item on every change.

also for performance reasons we'd probably pretend that we have a connection to any domain we have in the database && which isn't blocked.

Using multiple items will make it harder to get a consistent overview. It's going to be hard to determine what items are still showing up-to-date information (unless we start working with collections, or something)

search.jabber.network shall we take this conversation into xmpp:xmppnetworkgraph@conference.igniterealtime.org?join

Alright.

I know that prosody trunk isn't affected by that issue, but I can't say since when

Ah it is since trunk from 24.02.24

a simple question: can a conversation that running on a server which only has ipv6 address be joined into the search.jabber.network?

yes.

we have full IPv6 support.