jdev - 2022-01-08

  1. Link Mauve

    qy, your response was wrong, what more would you want?

  2. Link Mauve

    You’re expected to respect the protocol, not invent your own one. ^^'

  3. Link Mauve

    There is indeed no mechanism for notifying of an error happening as a result of an error or result stanza.

  4. Zash


  5. Link Mauve

    qy, note that in the case of caps, it’s kind of adversarial as if the server didn’t verify the hash, anyone could poison the cache with invalid data.

  6. Zash

    FWIW Prosody ignores the hash in the response and calculates it itself for cache keying

  7. Link Mauve

    Oh, so it could like, intercept all disco#info results ever, and build a caps cache, and automatically reply to all other requests?

  8. Link Mauve

    Ah no, because of the node part.

  9. Link Mauve


  10. Link Mauve

    Now that the bookmarks situation is solved, let’s migrate to ecaps2 too.

  11. Link Mauve

    It will solve all problems and be great!

  12. Zash


  13. qy

    Link Mauve: no i just meant some "im rejecting this response" message wouldnt hurt

  14. qy

    If it's a thing that happens it makes it impossible to debug incorrect implementations for example

  15. qy

    So i _think_ i've done it now but who the damn hell knows

  16. qy

    > Zash wrote: > FWIW Prosody ignores the hash in the response and calculates it itself for cache keying So it wasnt even an issue, goddamn it

  17. Sam

    Link Mauve: I just saw that you added block size support to mod_tcpproxy, thanks; immediately fixed an issue I was about to run into before I knew to ask :)

  18. Sam

    I don't understand the lua beyond copy-pasting and modifying it to take the endpoint from the config file. Can you (or maybe MattJ) confirm that it doesn't actually close the connection if you send the ibb <close>? I'm getting the connection, but having trouble in my read loop because I never get an EOF or anything to shutdown on

  19. Link Mauve

    I’ve never used this module, only fixed this blatant violation of XEP-0047 I found yesterday.

  20. Sam

    Ah gotcha; thanks for that

  21. Link Mauve

    Note that it still isn’t used, you can still get a <data/> containing more data than the requested block-size.

  22. Sam

    I can close the connection on my end I guess and ignore the resulting "read from closed connection" the read loop will get. Feels weird though that prosody is leaving it hanging or some other weird thing is going on and I can't tell it's closed.

  23. Sam

    (which works, the test passes and I get back the same data over TCP that I originally wrote over IBB)

  24. Sam

    Also, there was a scripting thing a while back that let you write small scripts (in Lua? Maybe it was related to Prosody?) to do XMPP things. Does that sound familiar to anyone? The internet is being useless, but I should probably find something like that to write integration tests against too since I'll eventually want tests that also create an IBB stream and send it to me as opposed to the other way around

  25. Sam

    Nevermind, I think it was Scansion; found it! (weirdly by searching for a completely unrelated term, that was very hard to find)

  26. Zash

    Do we need a tools category at https://xmpp.org/software/ ?

  27. MattJ

    I think so

  28. Zash

    https://xmpp.org/software/libraries/ > title: XMPP Libraries & Tools 🤨️

  29. MattJ


  30. emus

    Zash, MattJ: yes that was me. but I think you can drop your tools here

  31. emus

    then we can change the domain

  32. emus


  33. wurstsalat

    emus: yes?

  34. Zash

    Where does the line between tool and client even go?

  35. Zash

    Let's drop everything and spend a few months developing a thorough taxonomy of software!

  36. emus

    wurstsalat: can we simply change the domain?

  37. emus

    Zash: Tool is jist something which does not clearly goes into the other category. e.g. badxmpp or mattj's migrator

  38. emus

    > Zash escribió: > Let's drop everything and spend a few months developing a thorough taxonomy of software! yes please!

  39. Zash

    a start: https://github.com/xsf/xmpp.org/pull/1040

  40. Zash

    badxmpp and migrator you say?

  41. wurstsalat

    are snikket server tools usable in stand-alone use cases?

  42. Zash

    Hm, what tools are you thinking of?

  43. wurstsalat

    nothing in particular

  44. defanor

    Speaking of integration testing, sometimes I think it'd be neat to have a repository with a bunch of tests for testing different implementations together, yet being lazy even to start composing anything like that. I think there's a name for integration testing events, something like "plug party" (though not that); a continuous/ongoing and automated version of that is what I imagine.

  45. defanor

    Found the word: it's a "plugfest".

  46. Zash

    Not ... Interop testing event?

  47. defanor

    I guess you can call it that if you don't like fun names.

  48. Zash

    You certainly do some things using scansion, since it's a thing that emulates a bunch of clients. E.g. s2s tests, run a play with two clients connecting to different servers and exchange messages and stuff.

  49. Zash

    There was the idea of adding a server mode, so it would act as a scripted server instead of scripted clients, to allow testing clients. But that's just an idea so far.