XSF Discussion - 2020-02-01

https://news.ycombinator.com/item?id=22202206

> Absent leadership from XSF also plays a role. This club now mostly cares about bureaucracy and following a set of self-imposed rules instead of developing a set of working standards that would allow XMPP apps to compete with the best messaging apps out there. That's why it is unlikely for any great product to appear under such guidance.

Auch

> However, the messaging features of these platforms are all nearly identical lol

search.jabber.network got an update: - Invalid language tags are now omitted from the UI and @lang attributes for accessibility - Language statistics are available at: https://search.jabber.network/stats#languages (thanks debacle for bringing it up) - There’s now an OpenSearch descriptor which should allow adding s.j.n as search engine to your browser (thanks to Zash for figuring out how)

Wooh

Ge0rG, can you please review this: https://github.com/horazont/muchopper/pull/50 specifically the URL regex

(and anyone else who’s interested)

(it’s also live on beta.search.jabber.network for visual testing)

How does it handle https://en.wikipedia.org/wiki/Prosody_(software) ?

How does it handle (https://en.wikipedia.org/wiki/Prosody_(software)) ?

badly

please URL encode your parenthesis in the MUC description :)

(Not a correction, two separate test cases)

or invent a more clever regex

I would like to thank browsers for not doing that anymore

yeah

I feel very clever for finding a solution to the "how to mix keyword highlighting and url linkification without getting in a terrible mess of HTML escaping" problem by joining the regexes together

ZOMG

jonas’: no mental capacity at the moment, sorry

jonas’: So now 'de, en' is invalid?

!XSF_Martin, it always was

<field var='muc#roominfo_lang' label='Language of discussion'> <value>en</value> </field>

it’s a text-single field

if multiple languages were intended, it should’ve been text-multi

What's the valid way if you support two langs? Two value fields? How do I teach my muc to have two?

!XSF_Martin, the valid way is to bring a XEP on the way which supporst that

my suggestion is to have a separate "secondary languages" field and let the primary language be the language which is used for the description and title of the room

I don't think I have the skills to write an xep, so in fact it is impossible 😂

!XSF_Martin, writing a XEP is easy

you copy the template and fill in the blanks ;)

stealing most of your stuff from other XEPs doing a similar thing

also, description text linkification is live now

Or you could write a custom markdown-to-XEP converter!

Oh yeah. Then I will get my Dr. soon. I just take a dissertation template and fill the blanks. 😇

But right now I'm fighting with another near impossible task. Creating a debian source package that will spit out profanity and profanity-nox. ✏

I didn’t even know that profanity had a X frontend

It doesn't have but it has support for some xscreensaver-stuff, notifications and a tray-icon. The normal debian-package has all this enabled and will pull in Xorg if you try to install it on a headless system

ah, I see

jonas’ [13:39]: > my suggestion is to have a separate "secondary languages" field and let the primary language be the language which is used for the description and title of the room And this is how you end up with overengineered protocols!

!XSF_Martin: my headless server has a significant amount of X libraries

Ge0rG: I'd like to avoid that if possible

apt install --no-install-recommends profanity :( Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: adwaita-icon-theme fontconfig gtk-update-icon-cache hicolor-icon-theme libatk1.0-0 libatk1.0-data libavahi-client3 libavahi-common-data libavahi-common3 libcairo2 libcroco3 libcups2 libdatrie1 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgpgme11 libgraphite2-3 libgtk2.0-0 libgtk2.0-common libharfbuzz0b libnotify4 libotr5 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 librsvg2-2 librsvg2-common libstrophe0 libthai-data libthai0 libxcb-render0 libxcb-shm0 libxcomposite1 libxcursor1 libxdamage1 libxfixes3 libxi6 libxinerama1 libxrandr2 libxrender1 libxss1 x11-common

Ge0rG, I’m open for other options. as a web service, I need to know which language is used for the description + title

Pango and Cairo. What could go wrong?

jonas’: is sjn considered a valid tag?

jonas’: https://tools.ietf.org/html/rfc7231#section-5.3.5

Martin opensuse .. 😉😁

It's the icing on the cake of horrible protocol designs

Ge0rG, no

Ge0rG, actually, Accept-Language is a thing I miss in xmpp

jonas’: Where? vCard (at least 4) has a language field

Or you mean like `@xml:lang` but multiple-choice?

Zash, yeah

@xml:lang, but like Accept-Language ✏

jonas’: `<headers xmlns='http://jabber.org/protocol/shim'><header name='Accept-Language'>en,sv</header></headers>`

Zash, try to stick that into an IQ

jonas’: `Accept-Language: en;q=0.9;level=1,sv;q=.9999;level=2` parse this

been there, was fun

better than css either way

Zash, "level"? You made that up, did you? Just to make it Turing complete eventually.

debacle: Accept has that

Zash, wow, I wasn't aware of that. But Accept-Language not? BNF in RFC 2616: Accept-Language = "Accept-Language" ":" 1#( language-range [ ";" "q" "=" qvalue ] ) language-range = ( ( 1*8ALPHA *( "-" 1*8ALPHA ) ) | "*" ) and the example: Accept-Language: da, en-gb;q=0.8, en;q=0.7 Not *that* bad.

yeah, Accept-Language is pretty tame

How do you weight the q value against the ordering of the elements?