XSF Discussion - 2022-11-09


  1. debacle

    moparisthebest mjk Twitter is to Mastodon what Whatsapp is to XMPP

  2. mjk

    #laconic

  3. debacle

    however: summit 2023-02 or no? :-)

  4. moparisthebest

    debacle: what app are you talking about

  5. debacle

    ;-)

  6. edhelas

    Would it be possible to enable MAM on this room ?

  7. mdosch

    edhelas: Looks like it is already enabled.

  8. edhelas

    🤔

  9. vanitasvitae

    goffi, I'm reading over your set of proposed XEPs right now 👍️

  10. vanitasvitae

    I filed https://github.com/xsf/xeps/pull/1243 with some fixes for the PTE proposal

  11. mjk jumps onto the typo hunting wagon > a new items

  12. goffi

    vanitasvitae: thanks. Yeah PTE needs polishing, I was in a rush to finish it due to grant deadline, but the main thing is there. I'll update it after council review if it's accepted.

  13. vanitasvitae

    mjk, good find, I added it to the PR if you don't mind 🙂

  14. vanitasvitae

    s/if/hope/ 😛

  15. mjk

    sure, that was my intention (as always, too lazy to log in)

  16. singpolyma

    lovetox: https://github.com/xsf/xeps/pull/1246

  17. Zash

    singpolyma, why does it change the item id there?

  18. singpolyma

    Zash: in which part?

  19. Zash

    https://github.com/xsf/xeps/pull/1246/commits/ff1334998262ff13e7c23756ae26e54712231970#r1018053372 (hope I can link to that)

  20. Zash

    id='current' is consistent with singleton nodes <https://xmpp.org/extensions/xep-0060.html#impl-singleton>

  21. singpolyma

    Ah, I thought this made the example more clear. It uses in the notification the same id that was used with the publish above. Using only 'current' would mean that a client receiving an even has no way to know if this version differs from what they have already fetched, but using any opaque id that changes on each publication then when you get an event you can check "is this the one I have?" and fetch if not

  22. Zash

    Is contentless notifications used?

  23. singpolyma

    The XEP says yes (and did before, I did not change that)

  24. Zash

    ( https://xmpp.org/extensions/xep-0060.html#publisher-publish-success-withoutpayload )

  25. Zash

    I see.

  26. singpolyma

    The UUID thing was lovetox's suggestion IIRC, last time we discussed this update here

  27. singpolyma

    Because with PEP you will get the notification every time you log in

  28. singpolyma

    and so it makes it easy to see "ah, yes, that's the one I already have"

  29. Zash

    That is an issue with all PEP nodes tho

  30. singpolyma

    Yes, but if it's a small node then content-ful notifications are fine. But if every time I log in I just get contentless notification that says "current" that means... nothing?

  31. Zash

    Do clients +notify for vcard4 currently?

  32. edhelas

    I do

  33. flow

    at some point we should really write down some best practices regarding PubSub(/PEP) event notifications. Not using 'current' seems sensible here, other XEPs do something similar

  34. edhelas

    flow THIS

  35. Zash

    Like, a design considerations informational thing?