XSF Discussion - 2018-09-07


  1. daniel

    Would it be a stupid idea to have the muc server include the caps hash in room configuration change messages?

  2. pep.

    I have a poezio plugin that pulls the config and diffs, when there's a configuration change :x

  3. Kev

    Meanwhile, in Isode chat: Edwin I shall not mention PRECIS, shall I Kev PRECIS is a story told to frighten young children.

  4. Zash

    If you don't behave, you'll have to investigate how IDNA2003, IDNA2008 and PRECIS interacts.

  5. Maranda

    😲

  6. Maranda

    Do I want to know..?

  7. Maranda looked at rfc-4013 yesterday and noticed all those "Errata Exists" / "Obsoleted By" 🙄

  8. lovetox

    there is a caps hash for rooms? Oo

  9. lovetox

    didnt know that

  10. Zash

    caps hash is a function of disco#info, so why notq

  11. MattJ

    Good idea imho

  12. lovetox

    the benefit is not that great though

  13. Zash

    Hm, where did that come from?

  14. lovetox

    are there many muc config changes that dont affect the disco?

  15. Zash

    I thought I saw an email but now I don't

  16. lovetox

    if you mean why i brought up that topic, daniel asked in this room if the hash could be in the 104 status message

  17. Zash scrolls up

  18. Zash

    Ah there, hidden in a ton of joins and parts

  19. lovetox

    i would say its useful if there is a common case where the hash is not changed although a 104 message was sent

  20. Zash

    There are some settings that have status codes, some that just change in disco, others that might not have anything in disco at all.

  21. Zash

    I think(?)

  22. lovetox

    yeah what are those that are not in disco

  23. lovetox

    for the others is a hash not useful because it would be different anyway

  24. Zash

    Duno

  25. Zash

    You wouldn't be able to get stuff by discoing anyways

  26. lovetox

    if i disco i except to get a disco, what do you mean?

  27. Zash

    wut

  28. lovetox

    if i disco i expect to get a disco, what do you mean?

  29. lovetox

    what is the "stuff" you are talking that i dont get

  30. Zash

    If something isn't in disco, you wouldn't get it via disco

  31. lovetox

    i doubt there is much in a room config, that does not affect the disco

  32. lovetox

    thats why i would be interested about what frequently changed option daniel thinks

  33. lovetox

    where this would allow him to skip a disco

  34. daniel

    lovetox, well first of it was just a random thought i didn’t think it all the way through. i just thought that muc configs are probably very similiar. for example most users (on my client) will probably just have the conversations default config

  35. Zash

    daniel: Name and stuff goes in there tho, so I'm assuming every room will be unique

  36. daniel

    yeah name is a problem with that

  37. lovetox

    and you still have the problem to discover the hash

  38. daniel

    so it probably doesn’t buy you much

  39. Zash

    Probably doesn't hurt much either?

  40. Zash

    Benchmark or it never XEPs!! :)

  41. daniel

    would would be cool would be a way to discover the caps hash on join or something

  42. daniel

    then i don’t have to do a disco query again and again

  43. lovetox

    thats to late daniel, you have to put stuff into the join presence that depends on disco

  44. lovetox

    like history query if there is no MAM

  45. daniel

    yeah i know. i also run the query anway to have a reliable way of telling whether a room exists

  46. lovetox

    every muc publishes the hash in a pep node, and clients subscribe :D

  47. daniel

    but anyway it feels stupid to again and again do disco#info on 10s of rooms that all have very similiar if not the same config

  48. Zash

    https://xmpp.org/extensions/xep-0230.html :D