XSF Discussion - 2023-05-15

> > To add to the "millions of XEPs" that XMPP already has (to quote someone on HN today) 😄 > > And yet no one says a word when yet another protocol comes out to solve a solved problem because the author didn't bother looking at what ready exists or assumed old == bad. sounds familar... ↺

>>jjrh : do your own thing with xmpp and lots of companies do exactly this > That is exactly what we do. We use XMPP for telecommunications signalling in the finance sector with a private XEP known as Openlink Cisco/broadworks does this and so does bria (though sadly they have broken stuff so you can't actually federate with them) ✏

I wish asterisk did xmpp better - the chan_jingle and mod_xmpp seem to be mostly abandoned

Openfire has a very old plugin for Asterisk integration, but I'm not exactly sure if a) it's still functional and b) what exacty its features are. We could have a look at reviving it, if you're interested.

Is there some unicode that is allowed in resources but not allowed in localparts? something something unicode version prep garbage?

> Conflicting bidirectional properties in input oh...

singpolyma, resources allow almost anything, so yes

not quite anything though, right? for example most newer emoji are not allowed in resources

but not emoji! that's just cruel

mjk: some emoji are allowed

the ones from BMP probably?

I expect so

right. I think those are even allowed in C++ identifiers :D

I ❤ unicode versions

mjk, if you're thinking of the restrictions in Prosody, those come from stringprep which is tied to unicode 3.2

it doesn't disallow emojis, it disallows unassigned characters in unicode 3.2, which might just be all emojis

Zash: not really, no particular servers in mind, but thanks for the reminder that "it's complicated" ✏

@emus and other Board members: I’ve created https://wiki.xmpp.org/web/Board-Meeting-2023-06-08 for the next Board meeting. Please note that I will be mostly offline until June 1 or so...

thanks