XSF Discussion - 2018-02-18

Is there any XEP where server replies to some specific disco requests on behalf of a user? Especially those queries against new caps.

New caps generare huge amout of traffic when one have a lot of contacts and conferences. As result sometimes it takes a few minutes to send one small text message right after after start of some new version of a client.

Just found xep 390. Looks interesting :-)

Yep. 390 says servers MAY support this. Sounds promising :-)

I am going to add its support to Psi regardless of experimental status.

rion, great!

rion, servers can also announce xep115

yes, I use it already.

Then i probably don't understand the issue

the issue is when caps of my client change to something not widely-known (or unknown at all) then my client is flooded by disco requests rendering it to unusable state.

interesting, that sound indeed like something for ecaps2

possibly even without explicit server support, just a PEP node with the disco#info result

jonasw, ^

Not sure if I would want the contacts service to intercept the requests and answer on behalf of the client, that that's also doable.

*but that's

jonasw: subscribed to ML, waiting for mod :)

rion, may I ask what's causing the change in disco#info result?

flow: usually new nightly builds :)

ahh, kk

A nice post mortem on Google Wave... https://jamey.thesharps.us/2018/02/16/how-not-to-replace-email/

as if we hadn't talked about wave a few days ago

ups, I meant, "as if they knew we talked about wave a few days ago" :)

Hello!

I'd like to ask something about XEP-0092: Software Version

It says: In order for a requesting entity to determine if a responding entity supports this protocol, it SHOULD send a Service Discovery (XEP-0030) [5] information request to the responding entity: without any mention of Entity Capabilities (XEP-0115) like other XEPs do. I wonder why?

Yagiza, probably because it was invented before.

Yagiza, actually, I think most XEPs do not mention optimizations like XEP-0115 or XEP-0390 explicitly; the exception is PEP, which relies on XEP-0115 to work

Maybe it's possible to update the XEP before it promoted to Final?

I don’t think that it needs to be mentioned.

if an entity supports 0115 or 0390, it will naturally do the optimization

jonasw, even XEP-0071 has that mention

Explicitly mentioning which optimization to use has the downside that it needs to be updated when a new optimization comes around

jonasw, so, you believe that mention XEP-0030 implies using XEP-0115 when available?

yes

jonasw, ok

or XEP-0390 for that matter

I would rather see those redundant mentions of xep115 removed from the affected XEPs

jonasw, what do you think about the xep390 optimization to move the disco#info result from the client to the server?

I'm just not sure if the behavior rion experiences is common. I wouldn't expect clients to receive a storm of disco#info queries when they update their caps.

flow, I think the optimization is specified

flow, so I’m not sure what you’re asking

flow, https://xmpp.org/extensions/xep-0390.html#rules-servers

jonasw, ahh cool, wasn't aware that it's already in xep390

jonasw, found a typo: sevrer

thanks

edhelas, Yes, I can certainly look at that (XEP-0376). I need to do some work on that, and maybe sketch an implementation too.

:)

then let's work together