XSF Discussion - 2017-02-18

Ge0rG: Another nice corner case in XEP-0045: https://community.igniterealtime.org/thread/60267

Flow: that sounds like you need some generic other-error handler for this

Ge0rG: other-error handler?

you mean a filter for the error presence? See linked commit

Flow: ah, right

Flow: but you should also be able to handle error presence after a join

Ge0rG: *error* presence after join? don't you mean unavailable presence?

I could imagine you send a presence update to the MUC and it gets rejected by s2s

Flow: that to

+1

*too

ahh right, patches welcome

MattJ: BTW https://github.com/xsf/xeps/pull/427 :)

Oberserve how I shamelessly created an ack section for CSI and added myself

Flow: I've finally fixed the yaxim tree mess, next thing is to migrate to android studio, then smack4, then patches

buuu, android studio

Flow: let's say gradle.

sadly there is no Non-Android-Studio+gradle option for Android development as far as I know

Which is much better than a python3 script that manually pulls in dependencies.

I should get back down. Trolling ain't no fun when you are sick. /me &

Hi, I need german translations for some popular XEPs. They should be named consistently and understandable. It is for a translation of conversations.im. You can write them direct into https://etherpad.net/p/TranslateConversationsDotImToGerman Thank you for your help.

xyz I guess you need translations for only the titles of the XEPs, not the whole XEPs?

Only titles, yes

Looking at it: my german is not good enough to help you out here, but I do wonder if it would be good to maintain the original title and add the german translation between brackets?

good idea I'll add the english ones.

any one you don't know how to translate? maybe I can explain a bit what it is about...

Entity Capabilies Fetches what the other clients possibilities

xyz: sorry I have to go, will be back in 30 minutes or so, I'll have a look then

OK thanks I thougt maybe here is someone who knows directly

New version of ISR-SASL2, now with TLS 1.3 0-RTT: http://geekplace.eu/xeps/xep-isr-sasl2/xep-isr-sasl2.html

And for when TLS 1.3 in servers and clients?

mimi89999: the day after tomorrow

😂😂😂

the good thing is that ISR does not require TLS 1.3

Kev, thoughts on how to enable reflection of outgoing messages when enabling carbons with bind 2.0?

I have a local protoXEP draft for extending the current carbons iq for that

But just realised it won't be useful with bind 2.0

Bind2 needs extending to optional bits - I think enough people have demanded it that it's necessary.

So we can just have another element that's negotiated there.

Sounds good

+1 :)