XSF Discussion - 2021-11-06


  1. marc

    emus: that's something for the XMPP newsletter IMO: https://joinpeertube.org/news#live-plugin-app

  2. emus

    marc: thanks, we have it in our list already!

  3. marc

    Ah :)

  4. emus

    marc: https://yopad.eu/p/xmpp-newsletter-365days

  5. marc

    emus: thanks 👍

  6. Zash

    Hm

  7. Zash

    As some of you may have noticed, I like XEP-0122

  8. Zash

    Thought: Define/register a type for XEP-0359 IDs?

  9. flow

    type?

  10. Zash

    XEP-0122: Data Forms Validation

  11. Zash

    A Type!

  12. flow

    ahh

  13. flow

    how would that type be different from the non-empty string?

  14. Zash

    It would be explicit what's expected, but not much else

  15. flow

    hmm, shouldn't that be obvious from the protocol specification?

  16. Zash

    Altho, origin-scoped ids...

  17. Zash

    Meh, boring!

  18. flow

    I think origin-id is not really relevant

  19. Zash

    I was thinking ad-hoc commands

  20. Zash

    Oh, I mean the (by, id) tuple of stanza-id

  21. flow

    hmm, wouldn't conveying what is expected be a better job for the human-readable description of the field?

  22. flow

    I wonder if we could establish a short form of (by, id) like id@by

  23. Zash

    id@room@host?

  24. flow

    well I think IDs are best assigned by the MUC service, so id@muc.host

  25. flow

    otoh, given that the id part may also contain '@', such a short-format may be not such a good idea