XSF Discussion - 2018-06-19

  1. jonasw

    I know I’m late with this, but go to bed Ge0rG.

  2. edhelas

    https://nl.movim.eu/?about#caps_widget_tab :)

  3. Link Mauve

    edhelas, why do you sometimes use a caps string and sometimes a name?

  4. edhelas

    because those information are directly coming from the DB and some clients are declaring their names similar to their caps string

  5. edhelas

    like Poezio for example

  6. edhelas

    (or it's a parsing issue on my side, which can also be the cause)

  7. labdsf

    I have stamped [WIP] on https://github.com/xsf/xeps/pull/666 so don't merge it yet

  8. labdsf

    I want to rework feature discovery, have an idea how to get rid of making OMEMO a special case

  9. labdsf

    basically drop pubsub depencency and just assume that device/resource supports ephemeral messages if it has ever sent an <ephemeral> tag

  10. labdsf

    when timer setting update is received, client must update its setting and if it has changed, reply with the same timer update

  11. labdsf

    now I have a question: is XEP 0409 (rounting-ng) incompatible with entity capabilites (XEP 0115)?

  12. labdsf

    how can I use entity capabilities at all if I send to bare JID anyway?