XSF Discussion - 2018-02-18


  1. rion

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

  2. rion

    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.

  3. rion

    Just found xep 390. Looks interesting :-)

  4. rion

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

  5. rion

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

  6. Seve

    rion, great!

  7. flow

    rion, servers can also announce xep115

  8. rion

    yes, I use it already.

  9. flow

    Then i probably don't understand the issue

  10. rion

    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.

  11. flow

    interesting, that sound indeed like something for ecaps2

  12. flow

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

  13. flow

    jonasw, ^

  14. flow

    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.

  15. flow

    *but that's

  16. marc

    jonasw: subscribed to ML, waiting for mod :)

  17. flow

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

  18. rion

    flow: usually new nightly builds :)

  19. flow

    ahh, kk

  20. Ge0rG

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

  21. flow

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

  22. flow

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

  23. Yagiza

    Hello!

  24. Yagiza

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

  25. Yagiza

    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?

  26. jonasw

    Yagiza, probably because it was invented before.

  27. jonasw

    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

  28. Yagiza

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

  29. jonasw

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

  30. jonasw

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

  31. Yagiza

    jonasw, even XEP-0071 has that mention

  32. jonasw

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

  33. Yagiza

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

  34. jonasw

    yes

  35. Yagiza

    jonasw, ok

  36. jonasw

    or XEP-0390 for that matter

  37. flow

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

  38. flow

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

  39. flow

    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.

  40. jonasw

    flow, I think the optimization is specified

  41. jonasw

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

  42. jonasw

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

  43. flow

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

  44. flow

    jonasw, found a typo: sevrer

  45. jonasw

    thanks

  46. dwd

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

  47. edhelas

    :)

  48. edhelas

    then let's work together