XSF Discussion - 2017-11-05


  1. daniel

    What process do I have to go through to get an account on the wiki?

  2. Kev

    Find an admin, give them a mail address and ask nicely.

  3. Kev

    (I can do it Right Now)

  4. Kev

    But only if you give me a mail address :)

  5. Kev

    Or not. AFK.

  6. jonasw

    but Ge0rG can do it too, daniel.

  7. Ge0rG

    True

  8. Ge0rG

    jonasw: re MIX, the section in https://xmpp.org/extensions/xep-0369.html#usecase-server-presence-update is pretty clear

  9. jonasw

    I think they could just send a refresh request whenever a user joins, too.

  10. Ge0rG

    jonasw: this is about after-the-join

  11. jonasw

    it doesn’t need that information, except for joins, does it?

  12. jonasw

    okay, wait, do you mean "join" like "joining a channel for the first time" or "join" like "a reconnecting client activiating MIX support"?

  13. Ge0rG

    "In normal operation a MIX participant's server will hold accurate presence status for the channel which it provides to clients when they are activated." - so my server will receive and cache (in RAM?) presence from all participants of all MIXes that all the abandoned user accounts on my server ever joined.

  14. jonasw

    because I meant the latter, sorry for being unclear

  15. jonasw

    it doesn’t have to.

  16. Ge0rG

    but that's what the XEP says.

  17. jonasw

    there’s no MUST in there

  18. jonasw

    or even SHOULD

  19. jonasw

    I see this as suggestion

  20. jonasw

    (can be useful to reduce the delay when activating clients)

  21. Kev

    I'm not sure this is right.

  22. Ge0rG

    Kev: "this"?

  23. Ge0rG

    So can somebody elaborate please?

  24. Ge0rG

    😐

  25. zinid

    Server tracking presences from whole world, what a great idea

  26. Ge0rG

    Maybe my reading of the xep is wrong?

  27. Kev

    Sorry Ge0rG; I'm busy here. No, I mean that the subscriber's server shouldn't be needing to cache the presence of all occupants, so we need to look at taht.

  28. Ge0rG

    Kev: thanks. I'll write another large pile of feedback soon, not yet sure whether to the list or just to Steve

  29. jonasw

    Ge0rG, to the list if it’s not editorial, please

  30. Ge0rG

    jonasw: 👍

  31. Ge0rG

    So I've finally read and understood the relevant parts of 313

  32. Flow

    Ge0rG, looking forward to your feedback on MAM

  33. Ge0rG

    Flow: pretty well written, except for my pet peeve on what exactly to archive

  34. Alex

    Reminder: https://wiki.xmpp.org/web/Board_and_Council_Elections_2017

  35. Flow

    Ge0rG, are you asking for precise rules on what to archive? Do we need that (now)?

  36. Ge0rG

    Flow: yes I am. I think we need them as part of message routing 2.0, which can be done after advancing 313

  37. Flow

    I'm not sure why those rules are important, besides optimizing the archives size

  38. Ge0rG

    Consistency of what will be seen by your client

  39. jonasw

    *clients

  40. Ge0rG

    Try to debug a user's "messages are lost sometimes" issue and you will understand

  41. jonasw

    Flow, the archive rules are inconsistent with the carbon rules, which leads to interesting differences between what’s seen by devices depending on the time ranges in which they’re online

  42. Ge0rG

    I'd like to see error responses to archived messages in the archive as well, so I can see on my other/ reconnected client that a message was bounced

  43. Ge0rG

    You need to ask the user half a dozen questions about their exact deployment before even guessing the possible cause...

  44. Flow

    got ir

  45. Flow

    *it

  46. Guus

    We're short on xsf board candidates for next yeat! No one else interested? Know anyone that might be interested?

  47. Guus

    Only a few more hours until the application deadline expires.

  48. moparisthebest

    Memberbot will have to be modified to accept write in candidates then we'll have to conscript someone

  49. MattJ

    Anyone free to last-minute recreate my wiki account? (MattJ - mwild1@gmail.com)

  50. Kev

    Done.

  51. Link Mauve

    For anyone who thought I would procrastinate too much, I made it!

  52. Zash

    Successful procrastination?

  53. Link Mauve

    I’d say more successful fight against it. ^^

  54. Ge0rG

    Wow, we've got more candidates for council than slots. This will be an interesting time

  55. moparisthebest

    Aw no conscription...

  56. Ge0rG

    Do we need to run an electron rally now? 😀

  57. Holger

    I'd also appreciate a new wiki account (I guess that got lost during the crash?) ... holger - holger@zedat.fu-berlin.de