jdev - 2020-04-08


  1. Martin

    Hey, I wonder how I should determine that files.mdosch.de is the upload component in the following reply. Shouldn't there also be an "

  2. Martin

    Hey, I wonder how I should determine that files.mdosch.de is the upload component in the following reply. Shouldn't there also be a name='HTTP File Upload' in the reply?

  3. Martin

    <iq id='9a012720-f6684ac1-c194bca9' type='result' to='go-sendxmpp@mdosch.de/test' from='mdosch.de'><query xmlns='http://jabber.org/protocol/disco#items'><item jid='files.mdosch.de'/><item jid='chat.mdosch.de'/><item jid='proxy.mdosch.de'/></query></iq>

  4. Ge0rG

    Martin: you do disco#info on each of the items

  5. jonas’

    the name is irrelevant in either case

  6. jonas’

    you need to disco#info to discover the features, as Ge0rG said

  7. Martin

    Ok, thanks.

  8. Ge0rG

    Martin: and then there is a <identity category='store' type='file' /> thing and a feature

  9. Martin

    Looks good, thanks.

  10. Martin

    http://jabber.org/protocol/disco#items'/

  11. Martin

    <iq id='048c76c7-345c4abf-644d0920' type='result' to='go-sendxmpp@mdosch.de/test' from='files.mdosch.de'><query xmlns='http://jabber.org/protocol/disco#info'><identity type='file' name='HTTP File Upload' category='store'/><feature var='http://jabber.org/protocol/disco#info'/><feature var='http://jabber.org/protocol/disco#items'/><feature var='urn:xmpp:http:upload:0'/><feature var='urn:xmpp:http:upload'/><x type='result' xmlns='jabber:x:data'><field type='hidden' var='FORM_TYPE'><value>urn:xmpp:http:upload:0</value></field><field type='text-single' var='max-file-size'><value>104857600</value></field></x><x type='result' xmlns='jabber:x:data'><field type='hidden' var='FORM_TYPE'><value>urn:xmpp:http:upload</value></field><field type='text-single' var='max-file-size'><value>104857600</value></field></x></query></iq>

  12. Ge0rG

    XML is much easier to parse when it's indented and colorized.

  13. flow

    lies!

  14. Ge0rG

    English is much easier to parse if it doesn't contain ambiguous words.

  15. marc0s

    hi, what would be the way for a client whose user is member of a muc to have available the different join/leave messages, even for when she's not present at the room? as I see it, there's no way right now

  16. marc0s

    the goal is to pretty print messages of the type `Alice left the group`/`Bob joined the group` along the history fetched from mam

  17. Martin

    > XML is much easier to parse when it's indented and colorized. Sorry, I just had the raw output at hand.

  18. Ge0rG

    Martin: you need a plugin that will XHTML-IM syntax-highlight code

  19. Ge0rG

    also `xmllint --format`

  20. Martin

    Ugh

  21. Martin

    I have bad memorys of XHTML im.

  22. Ge0rG

    marc0s: there is no way to do that yet.

  23. Ge0rG

    marc0s: if it's a private room and MAM is used, being online/offline isn't as important as being a member of the room

  24. marc0s

    Ge0rG, good point. It's a private room as well as a private instance, so _maybe_ logging the affiliation changes (with a server-side mod) into the archive is Not That Bad™

  25. Ge0rG

    marc0s: yup

  26. ali

    nnnnn

  27. lovetox

    marc0s, there is something easier

  28. lovetox

    just display all members in the groupchat roster

  29. lovetox

    so a user will always see if someone is not there anymore if he looks at the roster

  30. lovetox

    no need for the join/left stuff

  31. lovetox

    hm though affiliation changes logged as message would be nice

  32. lovetox

    but its a presence, too bad