jdev - 2021-07-23

  1. Martin

    Moving here from prosody@. jonas’: Do you think this would be sufficient? https://paste.debian.net/1205341/

  2. jonas’

    Martin, what about <foo:proceed xmlns:foo='urn:....'/>?

  3. Zash

    we don't do that here.jpg

  4. jonas’

    Martin, what about <failed/> as opposed to any other random garbage you might get? :)

  5. Zash

    fail-tls.badxmpp.eu ?

  6. Martin

    Ok, checking for failed would be easy. Not sure about the foo.

  7. Martin

    Can I haz foo.badxmpp.eu?

  8. Zash

    Martin, xml prefix stuff?

  9. moparisthebest

    what about break-ejabberd.badxmpp.eu that sends `<features xmlns="http://etherx.jabber.org/streams"><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls></features>` instead of `<stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls></stream:features>` :D

  10. Zash


  11. moparisthebest

    (prosody is fine with either)

  12. Zash

    !praise libexpat

  13. Zash

    moparisthebest, surprisingly easy (I say, before testing)

  14. Zash


  15. moparisthebest

    ha, awesome, now that's some quick turnaround

  16. Link Mauve

    Can I haz xmpp:unprefixed-stream.badxmpp.eu too?

  17. Zash


  18. Zash

    Would need to find a point much earlier when that's accessible and can be overridden

  19. Martin

    Zash: > Martin, xml prefix stuff? If this is used somewhere it might be handy to check whether implementations cope with it.