XSF Discussion - 2019-01-15

hi

Hi

hey

hola

Привет

おは

Ola

hyvää päivää

I'm so glad that we've spend blood, sweat and tears in developing this protocol that makes it possible for us to have this high-quality conversation.

Is there anyone that is interested in staying at the Thon EU hotel for the summit/FOSDEM, that has not reserved a room yet, has not received any feedback from me, and is not winfried or @mattj? Please speak up now, as both time, as well as room availability, is running out!

(also, please join summit@muc.xmpp.org)

暇なやつら

Also, if you attend the summit, please make sure that your name is listed in https://wiki.xmpp.org/web/Summit_23#Summit_Participants (as this is the list that I'll use to arrange for access to the building). Please don't expect me to complete that list from memory!

(and again, please join summit@ - this concludes todays cross-posting)

Здравеите.

How much effort is it to put a banner or something on the inbox version of a spec when it gets accepted or rejected, to say so (and possibly point to the current version). I assume that's more work for the editors but it'd be great to have an idea of what's happened with stuff in the inbox as they're never removed (right?)

pep., you "just" need to patch the .xsl file in the xeps repo to allow for that

however, it would be nicer to have actual rediercts

I wouldn't mind having just a note "hey this is now live at XXX", or "This has been rejected, see <thread>" or something

yeah, would be a good way imo

you need to: - draft a format how to put t hat into the protoxep xml file - modify the dtd to allow it - modify the xsl to use it

Or maybe that can be a bug in the tracker

sure

Is that just an editorial thing or is it process or?

https://github.com/xsf/xeps/issues/738 here!

Is XMPP using BE or AE English in identifiers? Speaking of `self-ping-optimisation`

I heard US not so long ago

Ge0rG, XEPs use AE

that’s written down in some xep

so it must be `self-ping-optimization` then?

I guess

Yeah, agreed

`sälf-ping-åptimizatjon`

:)

`ſelf-pinng-opptimeisaschion` ✏

jonas’: what's that? en-DE?

Ge0rG, just like Zashes en-SV, yes

Let's re-write all the specs into Swänglish

Engrish please

that’s what we have UTF-8 for

セルフ・ピング・オプチミぜーション ? ✏

https://op-co.de/tmp/xep-0410.html - https://github.com/ge0rg/xeps/tree/xep0410 - feedback is welcome.

I assume I shouldn't PR that during the LC.

a diff would be good nontheless

jonas’: more of a diff than in the github link?

yes, because I have to look at each commit individually

If I had the tooling to make a rendered diff, I'd gladly do so.

an XML diff which includes all three commits would be good

just do a PR though, you can accumulate all your LC feedbac kthere

jonas’: https://github.com/xsf/xeps/compare/master...ge0rg:xep0410?expand=1 maybe?

that look sgood

left a comment on the second commit

jonas’: https://github.com/xsf/xeps/pull/739

which github nicely inlined into that pr, amazing

say about github what you will, the tools *are* amazing

btw, has xmpp bidi support?

not xep-0288 the other bidi

the other bidi?

right to left

and vertical

That would be up to the text rendering in each client, would it not?

yes, but is it encoded?

I guess not

do i need xhtml-im for thatm

or is it a language code thing?

Yeah I was wondering if xhtml-im included such a thing

I thought Unicode dealth with that

yes, looks complicated

Language is complicated

‮ What's the problem?

no no no

rebbaj looks good

do we need to update xep-0167 with reference to xep-0371 and deprecate xep-0176?

or is it just me that don't understand that stuff?

hi

my friend has configured sslh, but in apache it comment it come from 127.0.0.1

yes

that is to be expected

zash and do you know how it can be condigured to show from what ip it come.

Zash:

I don't think it can

im gonna ask my friend he follow guide from user from this xmpp.

my friend comment he use this guide from here: wiki.mattrude.com/SRV_records_for_XMPP_over_TLS

@mattrude are you online