XSF Discussion - 2019-01-23

Please select your menu for the XSF Dinner here: https://goo.gl/forms/hEtClRjLu7QqFkwS2 No selection => no food for you.

> Wow, I can even recognize Tarkin now! Grand Moff Tarkin! 😎

Andrew Nenakhov: yes, I was speaking of you! 😁

Hi guys. Did the Council review https://mail.jabber.org/pipermail/standards/2019-January/035595.html ?

You should probably ask for it to be explicitely on the council's agenda. Also 390 is not yet Draft so you can directly ping the author. Have you talked to jonas’ about it?

(I mean, you can ping him you, you don't have to do in private :)

Does he visit this muc? what's nickname?

I just pinged him for you

ah good =)

ping him here*

ah I didn't notice he is here. Just found :)

jonas’: ;)

He's pretty much everywhere 🙂

We're all pretty much eveywhere..

it's Neustradamus who is everywhere

including my xmpp:psi-dev@conference.jabber.ru?join -) ✏

rion, do I understand correctly that your proposal is to specify these modules basically: https://modules.prosody.im/mod_cache_c2s_caps.html https://modules.prosody.im/mod_auto_answer_disco_info.html ? ✏

We are all instances of the same chat bot

pep.: I read it as client side caching of the server caps

yes I'm Interested about client-side caching.

I see

my initial intention was to optimize service discovery while searching for http upload service.

> We are all instances of the same chat bot (Y)

rion: I like your suggestion, and maybe we can also get a recursive disco info from our server initially, to spare round trips

rion, talk with edhelas too, he wanted to do that too.

i mean yes caching would be nice

but thats like a baby step

to ONLY cache the server disco info

i guess you mean domain with that

on start i query all the services/components

and my account

so if there is a solution proposed it should include all these components

i find the idea of maybe a IQ get request nice

that returns for all components and my account the hash

so we reduce it from around 8 disco#infos, to one little IQ

just hacked 0084 in 0060

publishing an avatar for a Pubsub node as a urn:xmpp:avatar:data and urn:xmpp:avatar:metadata items in the node

boom Avatars for Pubsub nodes unlocked, it's ugly but it works, just have to be sure that the deliveries doesn't contains the payload

Wouldn't it have been better to put that into the metadata?

Zash, sure would.