XSF Discussion - 2023-02-12

> Google use it for their Google Cloud Messaging. Facebook use it for Facebook Chat integration. NATO use it for tactical chat. Thousands of companies use it for their enterprise instant messaging. Millions of devices use it to interconnect. The IETF use it in their meetings. One of our Board members uses it to talk to his mother. This faq entry tastes stale

Yes, more then one use it to talk to their mother, and the IETF switched?

is the fix to this pull requestable?

I expect so. I'm happy to draft something to propose maybe. I just was reading the FAQ and this one stood out to me

https://xmpp.org/extensions/xep-0425.html the reason here is optional right? It doesn't seem to say. And the schema seems off

(Message moderation)

The reason message? Sure, I'd assume so.

That's what I would also assume, but it doesn't say. I'll try to find wording to PR

« Consider a situation where a user sends a message that may be deemed inappropriate by a groupchat moderator. The groupchat service will append a Unique and Stable Stanza IDs (XEP-0359) [4] stanza ID to the message before relaying it to all participants. » Does this count as a MUC advertizing Message Moderation always providing stanza-id?

Sounds that way

Has anyone considered running a public incoming TLS relay to enable people to run XMPP servers from behind CGNAT ? If there's any prior art I'd like to know about it

Think "please give me a random subdomain and if XMPP connects on port 443 or 5222 or 5269 with that subdomain, pipe the bytes to me"

It's not xmpp specific, but at least one jmp customer is using hoppy network for this

Ah haven't heard of that, I think cloudflare has a product like this

Oh yeah, at that level there are a couple dozen TCP tunneling things. Cloudflare indeed runs a free one

It's nothing you can't easily set up now with some technical knowledge but I'm thinking something fully automated at the level of being able to bundle it with Snikket, and start hosting a server without knowing what DNS or port forwarding is

I think you could reasonably restrict it to XMPP without MITM'ing TLS and so prevent abuse and maintain privacy

moparisthebest: I've had a "host at home" plan on the roadmap for Snikket hosting for some time, sounds similar

We also looked into it for Prosody years ago, but at the time it was a different story with TLS so much harder

Yep, now once you assign the random subdomain you'll just automatically forward letsencrypt challenges to them and it all just works

MattJ: did you have anything written down or any thoughts about it, and or a better chat to move this to, if not can use xmpp:xmpp-server-app@code.moparisthe.best?join