XSF Discussion - 2018-07-03

  1. Ge0rG

    So I found another corner case logic bug where I was detecting "other device activity" before "is this a MUC reflection of my sent message", leading to suppression of notifications when I was active on a MUC.

  2. Holger

    Ge0rG: The intent was suppressing yaxim notifications while using the desktop client and the effect was suppressing yaxim notifications after sending MUC messages with yaxim?

  3. Ge0rG

    Holger: exactly

  4. Ge0rG

    The code processing the different kinds of messages, in the right order, is mere 170 LoC, but it's got really much implicit structural knowledge about processing dependencies in it.

  5. Ge0rG

    and now one mire item ✎

  6. Ge0rG

    and now one more item ✏

  7. Holger

    Ge0rG: I wasn't aware yaxim shuts up when detecting other device activity. For how long?

  8. Holger

    Ge0rG: And do you also still treat carbons differently?

  9. Ge0rG

    Holger: that's a recent feature in the beta, not yet in the official releases. 144s, like Conversations on "short"

  10. Ge0rG

    Holger: no, there is no difference any more, except for carbons of ?OTR-stuff, which get dropped

  11. Holger

    Ge0rG: Ah. Sounds good.

  12. Ge0rG

    Hm. There is still some code to mark carbons as "already read", but I'm not sure if it's actually effective

  13. Holger

    144 sounds like a result of in-depth scientific research 🙂

  14. Ge0rG

    Uhm, yes.