XSF Discussion - 2018-11-21

  1. Link Mauve

    (Moving from council@) “17:19:29 jonas’> we do have the luck to have a huge stash of disco#info replies from both servers and (a bit outdated) clients if you want to make a survey”, where can I find that? I also have the ones collected by poezio, but at least one third doesn’t validate, most likely because poezio forgot to put the @xml:lang in it…

  2. jonas’

    Link Mauve, https://github.com/xnyhps/capsdb/

  3. Link Mauve

    Oh, nice.

  4. jonas’

    aioxmpp has native support for reading and writing that format ;-)

  5. Link Mauve

    I guess I’ll merge mine into it.

  6. jonas’

    sounds like a plan

  7. Link Mauve

    jonas’, none of them have an @xml:lang, do they still validate correctly?

  8. jonas’

    at least one does have one (a grep on it shows it)

  9. Link Mauve

    Should I contribute only the ones from poezio which do validate, then?

  10. lovetox

    what this could be used nicely is to test your hash algo

  11. Link Mauve

    Or try to guess the @xml:lang?

  12. jonas’

    Link Mauve, I am confused, why guess it?

  13. Link Mauve

    jonas’, because we apparently didn’t store it.

  14. jonas’

    Link Mauve, or it wasn’t present

  15. flow

    I'm not sure if capsdb would give a realistic picture of the disco#info feature in disco#info replies situation: It appears to contain mostly non-node query results from clients, wheras, for example, ejabberd does not include it in its MUC component, and, while Smack would include the feature in non-node queries, it does not enforce that it is included in disco#info queries against nodes

  16. jonas’

    flow, for server-side things, I’d fire a search using the muclumbus crawler

  17. flow


  18. Ge0rG read that as "non-nude query results"

  19. Maranda doesn't wanna know.

  20. Neustradamus