jdev - 2024-06-10


  1. moparisthebest

    singpolyma, lovetox: are these bugs in gajim, old Cheogram, new Cheogram, the specs, or all of the above 🤣 https://share.snikket.de/LcWH7RpJETtTXSlRMrByMsXg/Imagepipe_3.jpg https://burtrum.org/up/35c480f5-5010-4ba8-ae99-f00548e3a97d/zb2rhnymb28ivanKNNkKe2wUkhpB4wqXwkHpr8tJ1FXtL3MN6.jpg cc debacle

  2. debacle

    Question is: Should `/me` work as `/me` in a reply as Gajim does? I believe yes, Gajim does it correctly.

  3. Kev

    245 says it should only be if \/me \ is the first four characters of the message body, FWIW.

  4. Kev

    245 says it should only be if `/me ` is the first four characters of the message body, FWIW.

  5. moparisthebest

    Yep, but it existed before quoting/replies

  6. Kev

    Yes.

  7. Kev

    I don't think one can claim that it's a bug to follow 245, was what I was meaning to say. Although I would agree that treating a reply as preamble rather than part of the 'body' in 245 terms seems sensible.

  8. moparisthebest

    By the letter of 245 gajim is wrong for sure, but what should be fixed 😁

  9. lovetox

    Am I missing something, none of your screenshots is Gajim or?

  10. lovetox

    A reply is not part of a body, and if you mean a fallback text, this is stripped in pre processing as the xep intends. So not part anymore of the body once it reaches display code

  11. lovetox

    I'm interested what Gajim does with a dumb quote before a /me

  12. moparisthebest

    lovetox: no screenshots of gajim but debacle said it was 1.9.0 and displayed the /me as intended

  13. moparisthebest

    Don't get me wrong gajim is clearly showing what the user wants to see i think, the question is what if anything we should do to specs/other clients to make them agree

  14. lovetox

    I think XEP 0245 just notes that /me is a thing and what a sending client intends with it

  15. lovetox

    i dont think we need to extend this XEP now for all kind of cases

  16. lovetox

    client devs can probably make their own decision here

  17. moparisthebest

    > I think XEP 0245 just notes that /me is a thing and what a sending client intends with it It doesn't though, it literally spells out: > Instead, the command is sent as-is (e.g., <body>/me laughs</body>) and the receiving client performs string-matching on the first four characters of the data included in the <body/> element to determine if the message begins with the string "/me ". If the client finds a match, the receiving client will show the message with a special presentation.

  18. moparisthebest

    In these cases the first 2 characters of <body> are `> `

  19. lovetox

    ... its a transfer protocol spec that mandates how things should be displayed to a user ..

  20. lovetox

    if a XEP does this, i take it as a kind of hint, where someone gathered at that point some input from the community and then tells me what the intention here is

  21. moparisthebest

    Many do

  22. lovetox

    but as of course how i display something to my users, does not break any other clients ..

  23. moparisthebest

    Like I said I think you made the right call here

  24. lovetox

    so in my mind its just a suggestion, and if i find something better, i obviously do htis

  25. moparisthebest

    Just disagrees with the XEP, probably would make sense to fix that

  26. moparisthebest

    But in the short term other clients could just do what you are doing...

  27. lovetox

    we will find many such things, all these reference xeps are kind of game changers that older XEPs didnt forsee

  28. debacle

    Please change the XEP, not Gajim :-)