XSF Discussion - 2022-01-16


  1. qwestion

    https://xmpp.org/software/clients/ no feature comparison matrix?

  2. moparisthebest

    No we hardly keep a list

  3. qwestion

    moparisthebest: so a documentation PR would be rejected

  4. qwestion

    moparisthebest: are you and your role mentioned on site? Many use real name yet xmpp handles is mostly what I see in rooms

  5. qy

    Is there a more up to date this anywhere? https://xmpp.org/schemas/index.shtml

  6. moparisthebest

    You can propose whatever, just seems there's been a lot of pushback for doing the bare minimum, something something just a standards org

  7. qy

    Also lol it's been so long since i've seen a shtml

  8. qy reminices to calling it "shitmail"

  9. moparisthebest

    Ha yea good times qy

  10. qwestion

    moparisthebest: matrix clients have good feature comparison

  11. qwestion

    Was useful

  12. moparisthebest

    qwestion: matrix is a company that doesn't do standards, just pushes marketing to get those investor dollars

  13. Zash

    There's the WIP https://github.com/xsf/xmpp.org/pull/986

  14. Zash

    Older render: https://linkmauve.fr/software/clients.html

  15. Zash

    Bunch of discussion in https://github.com/xsf/xmpp.org/issues/212

  16. moparisthebest

    qwestion: this unfortunately named website has some feature comparisons https://joinjabber.org/clients/gnulinux/

  17. Zash

    Having attempted to make a feature comparison table once, I can say that it's a lot of not very rewarding work to keep them up to date and stop everyone from turning it into marketing vehicle for their particular software.

  18. Zash

    It gets outdated pretty quickly and then people get either misled or unpleasant about it.

  19. Zash

    Also hard to compare things sometimes. And comparing XEP numbers isn't really optimal

  20. qy

    E.g. where might i find a theoretical xsd for the old omemo spec

  21. qy

    But also, every other xep

  22. Zash

    https://github.com/xsf/xeps/ ?

  23. Zash

    https://github.com/xsf/schemas ???

  24. qwestion

    > Having attempted to make a feature comparison table once, I can say that it's a lot of not very rewarding work to keep them up to date and stop everyone from turning it into marketing vehicle for their particular software. > It gets outdated pretty quickly and then people get either misled or unpleasant about it. Wiki where changes get approved?

  25. qwestion

    And clients devs/reliableenthusiasts are expected to fill their own details

  26. Zash

    What, create more bureaucracy? That'll just make it even more outdated.

  27. qwestion

    And clients devs/reliableenthusiasts are expected to fill their own clients details

  28. Zash

    The current idea is that client projects get to fill in their stuff in files that they serve, that can be collected and mangled into whatever you want.

  29. Zash

    See https://github.com/pulkomandy/xmpp-doap

  30. qy

    > Zash wrote: > https://github.com/xsf/xeps/ ? > https://github.com/xsf/schemas ??? So, latter has e.g. no mention of omemo/axolotl, and former... i _guess_ i could parse out schemas in a hideous manner, but that seems evil

  31. qy

    I presume its only missing from the latter because experimental?

  32. qy

    https://github.com/xsf/schemas/issues/5 oh

  33. qy

    >2019

  34. qy

    Wow

  35. qy

    ```curl https://xmpp.org/extensions/xep-0384.xml | xq '.xep.section1 | map({(.["@anchor"]): .cod e}) | add | .schema' -r``` teehee

  36. qwestion

    > Having attempted to make a feature comparison table once, I can say that it's a lot of not very rewarding work to keep them up to date and stop everyone from turning it into marketing vehicle for their particular software. > It gets outdated pretty quickly and then people get either misled or unpleasant about it. How Wikipedia manages to make so many sw comps? Maybe it should be done there too, as many clients don't have a page? Not notable enuf?

  37. qy

    Zash: if i used that to dump a schema for every xep under the sun, and shoved it in a PR, would it have any hope of going anywhere?

  38. qy

    It "works", i just compared 203 to delay.xsd from the schemas page

  39. qwestion

    Any client where I can "select all" msgs or shift highlight many msgs?

  40. qwestion

    Perhaps privacy friendly way to translate

  41. Zash

    qy, only one way to find out

  42. qy

    I've dumped them, i'll keep them to myself unless anyone's interested

  43. Zash

    Not my department anyway, not the one to ask.

  44. Neustradamus

    To have XMPP URI support on GitHub, please take your voice too: - https://github.com/github/feedback/discussions/10162

  45. wurstsalat

    qy: why to make a PR?

  46. wurstsalat

    qy: why not make a PR?

  47. qy

    wurstsalat: i feel like it'll snowball and i'll end up spending way more time and effort than i intend. That's normally how nontrivial PRs go for me and it's kinda put me off them...

  48. qy

    My intention was mainly just to see if i could autogen c++ bindings for every xep and hence have somewhat much neater code

  49. qy

    Turns out i can autogen, but it's not exactly neat

  50. dwd

    qy, C++ client library?

  51. qy

    Client app, but yeah i was thinking of breaking that bit off into "libXEPs" or something

  52. dwd

    qy, Which one?

  53. qy

    weechat-xmpp

  54. rion

    Which part of standard describes it's wrong to to take into account resolved via SRV hostname while validating xmpp-starttls certificate? I see Conversations and Gajim ignore the hostname during validation.

  55. Daniel

    You don't have a trust chain between something the user entered (jid domain) and the hostname

  56. Daniel

    Unless you do and then Conversations does take it into account

  57. MattJ

    rion, https://xmpp.org/rfcs/rfc6120.html#security-certificates-validation-server

  58. flow

    rion, if an attacker is able to spoof the SRV records, then clients using the target of the SRV record to validate the TLS certificate would easily authenticate against an attacker controlled service

  59. rion

    true.

  60. emus

    ralphm - I wrote you a direct message. Did you receive it?

  61. emus

    ah nevermind, I will reach out to board via mail directly

  62. moparisthebest

    rion: https://wiki.xmpp.org/web/The_Knight