XSF Discussion - 2023-11-30

  1. glitchdigger

    oi Alex

  2. glitchdigger

    unban me man wtf

  3. glitchdigger

    like i said in the chat, I gave you fair play on the channel rules

  4. glitchdigger


  5. glitchdigger

    ive supported loki and am good person. dont ban me just cuz i argued w you for 30 seconds

  6. glitchdigger


  7. Guus

    At what point is it permissible to 'motivate' new council and board members to provide a bio for the website, by suggesting that one will be provided for them ]:) if one is missing?

  8. Guus eyes fishbowler

  9. Guus

    As an aside: since being called out for it being empty, I've been adding a new job listing to https://xmpp.work every day in the last few weeks. Today was the first time that I didn't immediately find a new job listing in the last 24 hours on LinkedIn that mentions XMPP.

  10. jonas’

    Guus, I suspect not every council/board member is even aware of that page, so informing them seems sensible.

  11. Guus

    This was my attempt at humorously doing so - it's only Fishbowler's that appear to be missing.

  12. Zash

    Reviewing and refreshing your old one probably doesn't hurt either :)

  13. Guus

    They're mostly fine, I think

  14. Fishbowler

    > Guus eyes fishbowler It's on the to-do list, I promise.

  15. Guus

    When Openfire closes a client stream with an exception, it seems to allow the client to resume that session using Stream Management. That feels counterproductive.

  16. Zash

    That sounds wrong

  17. Guus

    Openfire's behavior, or my qualification as that being counterproductive?

  18. Zash

    The former

  19. MattJ

    Guus, any close of the stream (i.e. with a </stream:stream> tag) should close the stream in such a way that it can't be resumed

  20. MattJ

    In contrast to the client disappearing without closing the stream

  21. Guus

    We have that for client-originating stream close, but not from the server...

  22. Zash

    Flip it!

  23. Zash

    Client-originated close should lead to a close from the server after all

  24. Guus

    Zash, are you suggesting to no longer close the Stream Management session when the client sends a `</stream>` ?

  25. pep.

    Rather that the server will answer a </stream:stream> in any case?

  26. Guus

    a, right.

  27. singpolyma

    > When Openfire closes a client stream with an exception, it seems to allow the client to resume that session using Stream Management. That feels counterproductive. While I agree this is wrong per spec, it sounds super useful

  28. singpolyma

    Instead of needing to do a whole new session just because of a syntax error or too big stanza

  29. MattJ

    "Hey, it's me again. I sent you that super big stanza, did you receive it? Nope? Okay, here you go:"

  30. MattJ

    Though admittedly that has happened without resumption too :)

  31. Guus

    If a stream is closed with an error, I think that's defined as an unrecoverable condition. Resumption in that case seems undesirable to me.

  32. singpolyma

    MattJ: yes, would need to be careful to not do that, heh

  33. pep.

    singpolyma, isn't this mostly useful for devs? When is it useful to be able to resume after a syntax error in non-dev environments?

  34. singpolyma

    Saver time, etc that's all, vs a full rejoin of all MUCs etc

  35. singpolyma

    You're right it's mostly in the case of bugs, but bugs happen in the wild

  36. singpolyma

    Do servers keep track of every directed presence you send during a session in order to be able to send unavailable when you close/fail to resume the session?

  37. MattJ


  38. tai

    Hi people, can someone tell me how to unsubscribe from the XMPP standards mailing list?

  39. Zash

    Hi tai. Most mailing lists have a header like this: List-Unsubscribe: <mailto:standards-leave@xmpp.org> which tells you how to unsubscribe.

  40. Zash

    In this case, send an empty email to that address to unsubscribe.

  41. tai

    Thanks. The emails I receive only have that cryptic `Info: Unsubscribe: %(real_name)s-unsubscribe@%(host_name)s` footer which I can't tell how to use.

  42. Zash

    Heh, yeah I too noticed this.

  43. tai

    I'm using an email alias to receive mails from the standards list so I suppose I'll have to find out how to send mails from my alias and then unsubscribe through that. :) thanks.

  44. cal0pteryx

    You can only leave if you really really want to (push an admin to do it manually for you)

  45. tai

    oh geez, that's quite complicated. I have no idea who to approach then.

  46. singpolyma

    PM me your email and I'll figure it out next time I'm at my workstation

  47. tai


  48. tai

    Can't PM you, PMs are disabled as I see.

  49. singpolyma

    oh, xmpp:singpolyma@singpolyma.net that's me

  50. tai

    ah perfect, thanks

  51. tai

    PM'd you.

  52. singpolyma

    hello everyone. I think I have at least list subscription and delivery management web ui working; https://mail.jabber.org/postorius/lists/

    πŸŽ‰οΈ 1
  53. moparisthebest

    Awesome, thanks singpolyma :)

  54. moparisthebest

    10k internet points if you can make it stop mangling mails and failing DKIM 😁

  55. singpolyma

    I'm much less familiar with mailman3 so we'll see what I can do. I'm sure there are many options. Right now I'm hoping to make sure archives at least start happening for new messages, figure out why the web UI says example.com, a few things like that

  56. singpolyma

    Later, heh

  57. MattJ

    Thanks singpolyma!

  58. MattJ

    One step at a time, but this is a big step forward πŸ™‚