XSF Discussion - 2024-03-03

  1. Daniel


  2. Daniel

    Who made this client comparison flyer? I would love to get the source file so I can bring it to our XMPP booth at the Chemnitzer Linux Tage

  3. cal0pteryx

    MattJ: ^

  4. MattJ

    Daniel: I have the PDFs and source files for all the printed materials, I'll send them to you today

  5. lovetox

    great comparison, everything is the same :D

  6. lovetox

    Could the author please remove the checkmark "Audio/Video" on Gajim

  7. MattJ

    That photo is actually of last year's edition, the new one has Monal supporting AV

  8. lovetox

    this is no in a state where i would advertise this to any user

  9. MattJ

    lovetox: the latest says "in progress" - no pressure ๐Ÿ˜…

  10. lovetox


  11. Wirlaburla cries in Psi+

  12. emus

    > Who made this client comparison flyer? I would love to get the source file so I can bring it to our XMPP booth at the Chemnitzer Linux Tage https://github.com/xsf/xmpp.org/issues/1349

  13. MSavoritias fae.ve

    hey cal0pteryx i saw the message you left here -> https://github.com/xsf/xmpp.org/pull/1348#issuecomment-1973891221 for the jabber.el doap file. so i wanted to ask: you say > Compliancer only recognizes RFC links to the IETF pages (like https://www.rfc-editor.org/rfc/rfc6120.html), so these should probably be swapped as well. this means that places that says ` <implements rdf:resource="https://xmpp.org/rfcs/rfc6120.html"/>` should be changed to be `https://www.rfc-editor.org/rfc/rfc6120.html` ? because i am seeing the gajim and dino doap file and both of them link to xmpp.org not rfc-editor also noob xml question: why is it http and not https? is it just a compliance thing? for the other xeps you mentioned from the output of the compliancer these are to be added to the doap file right?

  14. cal0pteryx

    MSavoritias fae.ve: maybe both kinds of rfc urls work, I'm not sure. The compliancer marked some rfcs as missing. Right, you have to add XEPs to the DOAP file, if your client supports those

  15. cal0pteryx

    Regarding http/https: this is a namespace, not necessarily a URL (afaik)

  16. MSavoritias fae.ve

    right i know. i just didnt know it would make that much of a difference. but i guess its literally an identifier so http is the correct one

  17. mathieui

    I am still not subscribed to members@ through my email address despite doing the dance in hyperkitty to request access (and the discussions do show on the web interface, I just donโ€™t receive anything)

  18. mathieui

    (but summit@ works fine on the other hand)

  19. mathieui

    NVM, apparently "receive emails from the list" is not enabled by default (nor disabled :/), it should be better

  20. moparisthebest

    singpolyma maybe ^

  21. singpolyma

    mathieui: i believe you had delivery disabled due to bounces right? So that's why ti was disabled? Or was that not you

  22. mathieui

    singpolyma: that was me but months ago and since then I registered again on the webaite, but as I said earlier, apparently I also had to tick a box, that is now done, so we will see

  23. singpolyma

    Let me know if it still doesn't work after yourve re enabled now