XMPP Service Operators - 2021-08-31


  1. Trbl

    all the xmpp clients look like absoulte ass

  2. Trbl

    all the xmpp clients look like absolute ass

  3. Trbl

    Dino is the only one that doesn't try to give me eye cancer

  4. Sam

    Gajim's gotten better. All the text is still tiny for some reason and hard to read, but otherwise it's okay (with the disclaimer that single window mode isn't the default yet, so you have to turn that on or risk the roster randomly getting lost on some other desktop)

  5. Trbl

    gajim reminds me of the early 2000's

  6. Trbl

    ... which is a step up from most other clients that look like they peaked in the 90s

  7. Licaon_Kter

    Trbl: > gajim reminds me of the early 2000's Really? https://gajim.org/img/news/workspaces-preview-1.png

  8. Ge0rG

    Trbl: you might want to join jdev@muc.xmpp.org and help the developers improve the UI then :)

  9. Licaon_Kter

    Trbl: fyi https://gajim.org/post/2021-08-27-workspaces/

  10. Trbl

    Ge0rG: damn, that looks good

  11. Trbl

    apparently im full of shit

  12. Trbl

    Oh, Licaon*

  13. Licaon_Kter

    Trbl: > Dino is the only one that doesn't try to give me eye cancer You can use One-window mode now too, and close roster and etc, it's Dino-like almost

  14. Licaon_Kter

    Hope you're not comparing to Gajim 0.16.9 from 2014 or smth

  15. Ge0rG

    With Pidgin from 2008.

  16. Licaon_Kter

    Even better :))

  17. Trbl

    i got 1.3.2 installed

  18. Trbl

    and it looks like ass

  19. Licaon_Kter

    ^^^^ > You can use One-window mode now too, and close roster and etc, it's Dino-like almost

  20. jonas’

    Trbl, watch your language please

  21. Licaon_Kter

    Trbl: just say 'donkey' instead

  22. Trbl

    https://chat.her.st:5443/upload/805cad6b852b3640d60a17edd9d4a1cf8190e207/o5m9yaW2unmO74w6TGtwoFMZ94XojvMz1QrJ0rRL/8b521149-afe5-4140-a05b-2d8c5ee3ec01.png

  23. moparisthebest

    the best part about XMPP is it's a standard and you can make/use a client that suits your taste

  24. moparisthebest

    because especially with regards to looks, opinions are like ***holes, everyone has one and most of them stink

  25. Licaon_Kter

    Trbl: > i got 1.3.2 installed > and it looks like donkey Who forces you to use it? Exactly,..

  26. Trbl

    ??

  27. Trbl

    im using dino

  28. Trbl

    you brought up version numbers

  29. Licaon_Kter

    đź‘Ť

  30. Licaon_Kter

    MattJ: the current invitation workflow in Snikket is 379+401 or has extra magic dust on top?

  31. MattJ

    No magic dust, just a specific version of 401

  32. Licaon_Kter

    You know I'm gonna ask: "what's specific?'"

  33. MattJ

    Revision 0.3.0 of the XEP

  34. MattJ

    Not revision 0.4.0 which is the same as revision 0.2.0

  35. MattJ

    Just XSF stuff.

  36. Licaon_Kter

    Ok, just wanted to be sure I know all the codewords to annoy Holger :)

  37. MattJ

    The latest revision shouldn't be implemented, it was just published because the XEP's original author didn't approve the changes in 0.3.0. A new revision is planned, but... time

  38. MattJ

    So either a new XEP or new revision will be published based on 0.3.0, the author basically said they won't be updating 401 again iirc

  39. Licaon_Kter

    Mmmkay, drama

  40. jonas’

    MattJ, wait what?

  41. jonas’

    when did they say that?

  42. jonas’

    because if they said that then council should figure out what to do with the XEP

  43. jonas’

    (which probably means publishing the 0.3.0 the people who actually work with 401 want)

  44. MattJ

    It was a little more complicated iirc

  45. MattJ

    Ge0rG was working on an update that involved splitting out the bits they didn't agree with into a new XEP, and a new 401 having just the stuff we agree on

  46. jonas’

    sure, something like that was also my recollection

  47. jonas’

    but that's all moot if the 401 author said they effectively abandon it

  48. MattJ

    https://gitlab.com/xsf/xeps/-/merge_requests/33?commit_id=9c522069a7d09de58b78ccae19c74bb232323c3c

  49. Ge0rG

    I vaguely remember splitting out the good parts from 0401 into their own XEP. Did I forget to submit it to the XSF?

  50. jonas’

    mmmm

  51. jonas’

    I wonder what happened to that

  52. moparisthebest

    Ah when did it move to gitlab

  53. Ge0rG

    https://xmpp.org/extensions/inbox/ibr-token.html

  54. jonas’

    moparisthebest, it didn't

  55. Ge0rG

    Ah, it became https://xmpp.org/extensions/xep-0445.html

  56. moparisthebest

    Nevermind main page explains it

  57. Ge0rG

    MattJ: does your onboarding flow match 0445?

  58. MattJ

    Looks like it does, apart from the namespace of the stream feature :/

  59. Ge0rG

    MattJ: you could advertise both on the server. problem solved :D

  60. MattJ

    Oh yeah, of course :D

  61. MattJ

    Did you update yaxim to do 0445?

  62. Ge0rG

    MattJ: no :(

  63. MattJ

    Well makes sense to do it on the server side first

  64. MattJ

    Hopefully that is the only change, I don't see anything else from a quick skim

  65. Ge0rG

    MattJ: OTOH, I'm not checking for the feature on registration anyway, because if there is a token URL, the server obviously must be capable

  66. MattJ

    Fair enough

  67. Ge0rG

    and the attack vector of "crafted QR code" has so many escalations that are much worse than locking up yaxim

  68. Maranda

    I remember being firmly against XEP-0401 the first time it was even discussed in XSF a few years ago, I wasn't exactly light on it back then. Didn't exactly change my mind.

  69. Maranda

    I remember being firmly against XEP-0401 the first time it was even discussed in XSF a few years ago, I wasn't exactly light on it back then. Didn't change my mind.

  70. Maranda

    It looked like a can of worms ready to be opened.