jdev - 2022-08-07

  1. lovetox

    Link Mauve, the doap files for extension

  2. lovetox

    i think they miss a name attribute

  3. lovetox

    or is that supposed to be added by some automation that transforms this into a html page

  4. lovetox

    like if you look at the one for gajim https://gajim.org/support/extensions/

  5. lovetox

    i think thats not so useful for people dont know by heart the xep numbers

  6. Link Mauve

    lovetox, you can pick those from the xeps.xml pretty easily though.

  7. Link Mauve

    I you need any metadata about the XEPs themselves, they’re all there.

  8. lovetox

    hm, but was there not a project who does the conversion to html

  9. lovetox

    im pretty sure we didnt develop this ourself

  10. pulkomandy

    I wrote the xslt to generate html. If you need something added there I can have a look

  11. lovetox

    pulkomandy, is there a github project?

  12. lovetox

    where i could open a feature request

  13. lovetox

    is there any client that does something special with https://xmpp.org/extensions/xep-0461.html

  14. lovetox

    i dont have a idea GUI wise what i should do with the information that a message is a reply to some other message

  15. lovetox

    ah i can pull metadata from the other message and display it, like time and username which sent the original messasge

  16. pulkomandy


  17. nav

    lovetox: Or do a tap/click to scroll/focus the original message into view.

  18. nav

    With reference to https://github.com/pulkomandy/xmpp-doap/issues/10, there is https://xmpp.org/extensions/xeplist.xml that gets generated via the Makefile, though given the format of the current DOAP samples, it would appear to be simpler to s/.html$/.xml/ on <xmpp:xep rdf:resource="…"/> which would land you on the relevant XEP .xml.

  19. nav

    Aside from the name, it would be nice to also pull the version number of the latest XEP, to compare with the implemented version.

  20. Zash

    A tool that compares XEP version numbers from DOAP with the latest ones would be really nice to have, so you can check if there's something that needs to be updated. Not that it's too difficult to wrangle both into csv and compare

  21. lovetox

    python command line tool would be ok? `$ doap-version-compare https://gajim.org/gajim.doap`

  22. lovetox

    and the you get all outdated xeps with info to the version?

  23. pulkomandy

    It seems xslt can load data from other xml files, I'll see if that works, if it does I can use it to load the xeps and get the title and latest version from there

  24. lovetox

    that would be great

  25. lovetox

    like one column with XEP newest Version

  26. lovetox

    and then one column with XEP Name

  27. pulkomandy

    Yes, something like that, I keep it in mind for next time I sit in front of a computer

  28. Zash

    xml2 < doc/doap.xml | 2csv implements @rdf:resource xmpp:version

  29. Zash

    curl -s https://xmpp.org/extensions/xeplist.xml | xml2 | 2csv xep-infos/xep number last-revision/version | grep -v ^xxxx,

  30. Zash

    slap some sed and diff on it and call it a day! 🙂

  31. nav

    I've hacked https://github.com/pulkomandy/xmpp-doap/blob/master/style.xsl to extract the title and abstract from the xmpp.org XMLs.

  32. nav

    (not without running into a spot of bother with xsltproc and switching to Saxon)

  33. nav

    I'll see if I can get the latest version

  34. nav

    Not difficult *if* the newest version is always the first <revision/> element.

  35. jonas’

    nav, that is guaranteed™

  36. jonas’

    nav, but even better, use xeplist.xml

  37. jonas’

    nav, https://xmpp.org/extensions/xeplist.xml that has that information readily extracted

  38. nav

    jonas’: It's more difficult to match against xeplist.xml

  39. jonas’

    what would be needed to make it easier?

  40. nav

    This is what I have so far: https://labs.navlost.eu/pub/doap.html

  41. nav

    jonas’: Four digit XEP numbers

  42. nav


  43. nav

    Ok, there goes my latest version:

  44. nav


  45. nav

    Source file: https://labs.navlost.eu/pub/doap.xml (note that it would render directly on the browser if https://xmpp.org/extensions had the appropriate CORS headers).

  46. jonas’

    nav, https://github.com/xsf/xeps/blob/master/tools/extract-metadata.py#L130 wanna change it?

  47. nav

    XSLT: https://labs.navlost.eu/pub/doap-style.xsl

  48. nav

    CSS: https://labs.navlost.eu/pub/doap-style.css

  49. nav

    jonas’: I like going to the individual XEP better because that allows me to extract the date of the implemented version (as well as the date and number of the latest version, which is in xeplist)

  50. nav

    I then put the date on the "title" attribute.

  51. lovetox

    great nav, that looks like good improvements

  52. lovetox

    one nitpick, can we name it "Version implemented"

  53. lovetox

    Use version sounds like some lib we use

  54. wurstsalat

    "Latest Version" "Implemented Version" sounds good to me :) nav, great to see somebody working on this!

  55. nav

    lovetox: Roger, why not. I've just uploaded a new version of https://labs.navlost.eu/pub/doap-style.xsl (cleaned up a bit).

  56. nav

    Better now? https://labs.navlost.eu/pub/doap.html

  57. nav

    wurstsalat: It was either this or doing the taxes. 😬

  58. lovetox

    i find wurstsalat suggestion better than mine

  59. lovetox

    would be great if you could do a PR against https://github.com/pulkomandy/xmpp-doap with your changes

  60. wurstsalat

    nav, good choice ;) yeah please do a PR! I have some styling ideas I'd like to try

  61. nav

    wurstsalat: I'm not touching Github with a bargepole. Here's a diff instead.

  62. nav


  63. nav


  64. Martin

    You may also git-email it to someone or a mailing list instead.

  65. aliex@exploit.im


  66. nav

    Martin: One is more of an XMPP type. 😊

  67. nav

    Not that I've seen an email (or for that matter, XMPP) address in that Github page anyway (though you can get them from the git log).

  68. nav

    Anyway, I'm working on making it possible to send patches via XMPP to GitLab & Gitea repositories, so you don't have to have an account to contribute.

  69. nav

    It is already possible to file bug reports via XMPP without an account on the relevant GitLab / Gitea server, provided that someone with write access to the project configures an appropriate XMPP endpoint.

  70. nav


  71. whiterok77

    hello friends