XSF Communications Team - 2026-01-16


  1. badrihippo

    > But if you have a draft, please drop it already Only what I shared earlier, but updating the headline about Movim

  2. badrihippo

    https://disroot.org/upload/019bc518-f1da-7881-8d8d-fbeb4ed1de0d/xmpp-highlights-2025-draft3.pdf

  3. badrihippo

    And thanks goffi, I will try to write these up and let you know if I need help!

  4. badrihippo

    Actually, can you tell me more about the e2e encryption with gateways? I don't think I've heard of that before..

  5. badrihippo

    Found this: https://libervia.org/blog/view/goffi@goffi.org/@/id/libervia-progress-note-2022-w45-MTdL

  6. gnemmi

    badrihippo, I really like what you have going on in there!. Pretty neat!.

    πŸ‘ 1
  7. gnemmi

    Please don't forget to add the Monocles Chat entry though!

  8. gnemmi

    Check the pad, arne added a pretty *on spot* Monocles Chathttps://pad.nixnet.services/x87ng-viRoGzVtjeIv7Luw# πŸ‘

  9. gnemmi

    Slidge ( from 333 chars to 220 ) -> "Slidge releases version 0.3.0: support for (optional) reaction fallbacks, gateway-wide settings moved to user-specific settings, check the β€œpreferences” command (adhoc or chatbot-style) and support for pronouns in VCards."

  10. gnemmi

    You can also safely remove all the "code named XXX" from all the movim entries

  11. gnemmi

    Here you go, just trying to easy up on the workload:

  12. gnemmi

    "Movim version 0.30: the biggest Movim evolution in years, includes multi-participant calls, reactions displayed in the detailed message view, Unicode 15.1, plenty of new emojis and avatar change when contacts adds a Story." "Movim version 0.31: implements NLNet funded simultaneous webcam and screen sharing." "Movim: version 0.32: One of the biggest releases ever made. It includes numerous fixes and features in the 3 major topics: instant messaging, social networking, and video conferencing."

  13. gnemmi

    "Movim version 0.30: the biggest Movim evolution in years, includes multi-participant calls, reactions displayed in the detailed message view, Unicode 15.1, plenty of new emojis and avatar change when contacts adds a Story." "Movim version 0.31: implements NLNet funded simultaneous webcam and screen sharing." "Movim: version 0.32: One of the biggest releases ever made. It includes numerous fixes and features in the 3 major topics: instant messaging, social networking, and video conferencing."

  14. gnemmi

    "Movim version 0.30: the biggest Movim evolution in years, includes multi-participant calls, reactions displayed in the detailed message view, Unicode 15.1, plenty of new emojis and avatar change on contacts new Story." "Movim version 0.31: implements NLNet funded simultaneous webcam and screen sharing." "Movim: version 0.32: One of the biggest releases ever made. It includes numerous fixes and features in the 3 major topics: instant messaging, social networking, and video conferencing."

  15. gnemmi

    That will help make some room for Libervia and Monocles Chat

  16. gnemmi

    Monocles Chat ( from 440 chars to 262) -> "Monocles Chat: Vcard profile editor which allows to share your profile as a simple business card via QR code. A chat overview calendar to easily jump to messages by date. Pin multiple messages. And β€œUser Tune” to display which song you are currently listening to"

  17. emus

    badrihippo: pretty neat! One suggestion can we have the proejcts icon? Logo next to their name or similar? To big, but as a visual reference

  18. badrihippo

    Thanks emus and wow thanks gnemmi for all the writing/editing!!

    πŸ€— 1
  19. badrihippo

    Yes, I was actually thinking of removing some of the screenshots as well in favour of project icons. You can't really make out much from the screenshots, so maybe I'll add them in only if it's something special like helping to explain how a particular feature works

    πŸ’― 1πŸ‘Œ 1
  20. emus

    badrihippo: will it be two pages?

  21. badrihippo

    > You can't really make out much from the screenshots I mean, at the scale it's going to be, printed on paper

  22. badrihippo

    > badrihippo: will it be two pages? Yes. One sheet of paper, front and back, folded into three

  23. emus

    > badrihippo: will it be two pages? Nevermind

  24. badrihippo

    https://disroot.org/upload/019bc5e1-5fe2-7a53-9f58-a9d9cea46f0b/9267e2fc-c4e2-432d-9f92-e3f52d357759.png

    ❀️ 1
  25. badrihippo

    That's how it'd work out when folded btw. In case you found the ordering a bit weird πŸ™ƒ

  26. goffi

    > Actually, can you tell me more about the e2e encryption with gateways? I don't think I've heard of that before.. Hey. I'm working on so called "Gateway Relayed Encryption". The idea is that the Gateway explains to the client how to encrypt data, and it then just root the encrypted payload. I've made a proposal which is in inbox (https://xmpp.org/extensions/inbox/gateway-relayed-encryption.html and https://xmpp.org/extensions/inbox/gre-encrypter-openpgp.html and https://xmpp.org/extensions/inbox/gre-formatter-mime.html) but at the end I'll directly propose a more generic version based on webassembly. I have an experimental implementation in the email gateway and the client part of Libervia for MIME/OpenPGP.

  27. emus

    I really love this!

  28. goffi

    yes the progress note explain that too.

    πŸ‘πŸ½ 1
  29. goffi

    route* not root of course :)

  30. emus

    > That's how it'd work out when folded btw. In case you found the ordering a bit weird πŸ™ƒ I didnt saw on my mobile pdf that theres a second page!

  31. badrihippo

    > I didnt saw on my mobile pdf that theres a second page! Oh I see πŸ˜…

  32. badrihippo

    > Hey. I'm working on so called "Gateway Relayed Encryption". The idea is that the Gateway explains to the client how to encrypt data, and it then just root the encrypted payload. I've made a proposal which is in inbox (https://xmpp.org/extensions/inbox/gateway-relayed-encryption.html and https://xmpp.org/extensions/inbox/gre-encrypter-openpgp.html and https://xmpp.org/extensions/inbox/gre-formatter-mime.html) but at the end I'll directly propose a more generic version based on webassembly. I have an experimental implementation in the email gateway and the client part of Libervia for MIME/OpenPGP. Thanks! The spec is helpful; I glanced through but will read it properly

  33. badrihippo

    So wait, you have a gateway for XMPP <-> SMTP and encrypted using OpenPGP? πŸ‘€

  34. goffi

    For the flyer there is no need to go into too much details, just saying that there is WIP on e2e encryption working with gateways should be enough IMHO.

    πŸ‘ 1
  35. emus

    badrihippo: Please, very small put the contributors names somewhere :-) Maybe also a license

  36. goffi

    > So wait, you have a gateway for XMPP <-> SMTP and encrypted using OpenPGP? πŸ‘€ Yeah, the client encrypt with OpenPGP in a way explained by the gateway, and the gateway route it to the legacy network.

  37. badrihippo

    > badrihippo: Please, very small put the contributors names somewhere :-) > Maybe also a license Oh yes! I'll do that all in the back cover along with a photo of the fancy looking 39c3 displays (by the way, is it okay to use that and whom should I credit?)

    ❀️ 1
  38. goffi

    With webassembly, it should work with any kind of network (including whatsapp, signal, etc.)

    πŸ‘ŒπŸ½ 1
  39. emus

    badrihippo: can we refer to getting started and also our specs page?

  40. badrihippo

    Sure. By specs do you mean https://xmpp.org/extensions/?

    πŸ‘ 1
  41. goffi

    I should propose webassembly related spec in Q1 2026 (but so many things going at the same time, it's hard to predict accurately, it's quite high on TODO list though).

  42. badrihippo

    That's actually really cool. So the SMTP side doesn't need to know anything and the client doesn't have to have pre-built special information either, it only needs to know how to follow instructions from the gateway

  43. goffi

    The SMTP side only knows sender/recipient and approximative size.

  44. goffi

    The Gateway only knows sender/recipient and approximative size.

  45. goffi

    The gateway only knows sender/recipient and approximative size.

  46. goffi

    For my current implementation, the client must know how to format email. But with the incoming webassembly thingy, it just has to know how to run the webassembly blob (and how to verify its origin).

  47. goffi

    and it won't be restricted to messages, can be used for anything (pubsub, file sharing).

    πŸŽ‰ 1
  48. badrihippo

    > For my current implementation, the client must know how to format email. But with the incoming webassembly thingy, it just has to know how to run the webassembly blob (and how to verify its origin). That webassembly part was making me a bit nervous until I read "and how to verify its origin". I assumed that means the blob will be cryptographically signed by the gateway in some way?

  49. badrihippo

    Anyway, maybe we should shift this to the main room or jdev as it's getting a bit off topic here πŸ˜… I'll write work is being done for e2ee in gateways, as you suggested

    πŸ‘ 1
  50. emus

    badrihippo: could you add some thin folding lines, too?

  51. badrihippo

    Sure. I think that's an option that can be enabled when rendering the PDF. If I could just figure out how to enable it (I will eventually)

    πŸ‘ 1
  52. gnemmi

    > Yes, I was actually thinking of removing some of the screenshots as well in favour of project icons. You can't really make out much from the screenshots, so maybe I'll add them in only if it's something special like helping to explain how a particular feature works Fantastic idea!

  53. emus

    But I think you can do both. Just have a small icon next to the title

  54. gnemmi

    That would be the ideal case. Maybe adding the project icon in front of the url that stands below each entry?

  55. emus

    I would prefer next to the title, but that is also okay.

  56. gnemmi

    Yeah .. I thought about that one too, but then thought that maybe that would be harder to pull from a layout point of view.

  57. gnemmi

    Still, as long as badrihippo manages to slap the projects logo, I'll be fine with the final outcome

  58. emus

    I leave it up to you πŸ™‚

  59. emus

    I like very much what I see

  60. emus

    already

  61. gnemmi

    Same in here. It's looking *really* well so far. Fantastic job by badrihippo!

    πŸ‘ 1