XSF Discussion - 2019-08-03

  1. lovetox

    jonas’, the http api uri in the examples of the api docs of muculumbus is wrong

  2. lovetox

    or not used anymore to be exact

  3. jonas’

    lovetox, which one?

  4. lovetox


  5. lovetox

    is in the examples

  6. jonas’

    both work

  7. jonas’

    jabber.network will give you a redirect of course

  8. lovetox

    yeah, still i dont think any http lib just autofollows redirects

  9. lovetox

    im also not sure i even want to implement something like that

  10. jonas’


  11. jonas’

    I’ll go and fix it soon

  12. lovetox

    yeah no hurry just wanted to mention it

  13. Ge0rG

    if only we had stable domains maintained by an organisation of sorts.

  14. lovetox

    jonas’, already 2200 mucs on muclumbus

  15. lovetox

    some weeks ago it was only 600

  16. jonas’

    unless there was a glitch, I doubt that’s treu

  17. jonas’

    there are 6.7k public MUCs in the db right now, where did you get the 2.2k from?

  18. lovetox

    thats all i get when i request all

  19. jonas’

    ah, it only returns MUCs with at least one occupant by default

  20. lovetox

    ah yeah :)

  21. lovetox

    but still weird that its always a round number

  22. lovetox

    its exactly 2200

  23. lovetox

    or i have a counting bug

  24. jonas’

    that sounds like a pagination bug

  25. Zash

    https://xmpp.org/extensions/xep-0060.html talks about a "cache-last-item" feature, but it seems to be undefined.

  26. Zash

    What's up with that?

  27. lovetox

    does anyone know a case where a error is returned with more than one error condition with namespace urn:ietf:params:xml:ns:xmpp-stanzas

  28. lovetox

    the rfc says an error must contain a condition, but does not say it must be only one

  29. jonas’

    the schema does not allow it at least

  30. Zash

    Multiple `<text>` is ok tho

  31. jonas’

    for i18n

  32. Link Mauve

    lovetox, I haven’t found any, when I ran xmpp-parsers on data extracted from the xeps repository.

  33. lovetox

    ok then i will support one error condition and one application error condition

  34. lovetox

    and multiple text elements

  35. lovetox

    parsing errors is a bit weird

  36. lovetox

    you have to iter the childs of error, and you dont really know what you are searching for, you only know what you dont search for

  37. jonas’

    for i18n

  38. jonas’

    wrong window

  39. Link Mauve

    It’s one text element, but in multiple different locales.

  40. Link Mauve

    It’s invalid for instance to have the same locale twice.

  41. jonas’

    that’s still multiple elements on the XML layer

  42. Link Mauve


  43. Link Mauve

    But not conceptually.

  44. lovetox

    so i looked into the xml:lang thing

  45. lovetox

    i expected every server issue only one text with the lang i set on the stream

  46. lovetox

    but as someone mentioned, and i saw it myself some server add also the "en" translation

  47. lovetox

    Gajim just takes the first text element and expects it to be in stream lang, so as this is obviously not good i checked expat for xml:lang inheritence

  48. lovetox

    seems the xml standard actually says to inherit that

  49. lovetox

    but i could not find any hint that expat actually does this

  50. lovetox

    BUT its stll very easy on client side

  51. lovetox

    at least with my node objects that my parser creates every node has its parent assigned

  52. lovetox

    so you just traverse up the parents until you find one with an xml:lang attr

  53. lovetox

    so still not seeing the can of worms that i supposed to have opened

  54. flow

    I find it actually very beneficial that entities also include "en" besides the receivers xml:lang in error stanzas

  55. flow

    Makes it easier to read XMPP traces being posted in your forum etc

  56. flow

    I think it would be even nice if the standard recommends doing so

  57. Ge0rG

    lovetox: lucky you have access to the whole hierarchy of elements from where you need the language. The parser I'm working with doesn't give me the elements above.