XMPP Summit - 2026-01-30


  1. mathieui

    emus: the setup was perfect today, I would not complain if there were mandarines instead of bananas (since I prefer mandarines), but there was plenty enough to eat in any case 😋

    ✔️ 1
  2. Thilo Molitor

    https://images.assettype.com/barandbench/2026-01-27/5ol8a72t/Meta__WhatsApp_complaint_.pdf

  3. Thilo Molitor

    Maybe we should use that when lobbying for decentralized systems...

  4. Thilo Molitor

    Heise article (in german): https://www.heise.de/news/Sammelklage-WhatsApp-Verschluesselung-angeblich-unwirksam-11156854.html

  5. emus

    (Sorry Thilo not to distrub your discussion) Would someone do me a favor an take the (small) pack of stickers today for tomorrows Fosdem? I also have to carry the handouts and wont be that early at the Fosdem.

  6. ralphm

    We have plenty of stickers

  7. Karel

    debacle, celeste, are you walking to the venue? If you let me know when you plan to leave the hotel, I could try to join you on the way

  8. emus

    > We have plenty of stickers Okay, still can someone help as I dont know how much I will have to carry

  9. jp

    Karel we go around 8:40

  10. emus

    Im running a bit late, but will be there in 20 mins

  11. jp

    Karel we are going now. See you there!

  12. Fishbowler

    Haven't quite escaped the NH yet

  13. Guus

    I'm planning to leave NH at 9:15

  14. mremond

    On my way

  15. Guus

    Forgot something in my room. I'll be down in two minutes

  16. Intosi

    We're back online with audio. Video will arrive shortly.

  17. Intosi

    https://calls.disroot.org/XMPPSummit28 for anyone who forgot :).

  18. singpolyma

    sealed sender and onion routing are one topic: no?

  19. mathieui

    We’re starting with a lightning talk from nicoco right now, FYI for the people in remote

  20. mathieui

    singpolyma, not necessarily

  21. singpolyma

    you can't do (useful) sealed sender without onion routing and I'm not sure what you'd accomplish with onion routing other than sealed sender/recipient. so it seems like they at least need to get discussed together

  22. mathieui

    singpolyma, I think daniel introduced it by talking about SASL anonymous

  23. mathieui

    but we’ll see

    👍 1
  24. singpolyma

    nicoco: I filed a ticket for myself for you at least now: https://soprani.ca/todo/533

  25. singpolyma

    I'm going to probably draft XEP soon for link preview. it's time now with three implementations

  26. Fishbowler

    https://nicoco.fr/summit28/ for the on-screen slides

    🙏 1
  27. mremond

    º

  28. mremond

    This person attempted to retract a previous message, but it's unsupported by your client.

  29. Edwin

    slidge.im seems to be down.

    ❗ 1
  30. singpolyma

    host gateway but not host server is totally doable with https://xmpp.org/extensions/xep-0225.html ;) I mean admin has to allow you a "component account" or whatever but that's all

  31. singpolyma

    I don't see how OMEMO to gateway is any kind of improvement. However, for the UX concern this is "easy" to solve by having the app detect it is doing OMEMO to a gateway jid and display differently to not promise e2ee (if they app indeed shows anything)

  32. singpolyma

    I'm not sure that designing based on "some client might not show what we want" is ever going to be sensible. There will always be some app that doesn't do what you prefer. All you can do is not suggest such a client from eg your gateway website

  33. emus

    Same point as yesterday: If you want to raise any point to the round, please tag it with SUMMIT

  34. emus

    nicoco: Will you be able to fix soon or will it take time?

  35. emus

    because I would like to drop a post

  36. singpolyma

    SUMMIT: if you don't deliver at least somehow via your server don't we lose all possibility of multi device message history?

    ✔️ 1
  37. edhelas

    > Same point as yesterday: If you want to raise any point to the round, please tag it with SUMMIT So we'll need to add #hashtags support in XMPP, new topic !

  38. mremond

    #hashtags mentions ?

  39. Edwin

    <tag xmlns='urn:xmpp:hashtag#1'>wibble</tag>

  40. edhelas

    Could be

  41. edhelas

    Would be also awesome to have them in vcards or descriptions, would really ease the search and discoverability feature

  42. MattJ

    singpolyma, ah, I just relayed you without knowing :)

  43. edhelas

    (Atom have already <category/> for that for Pubsub Social items, so that's fine)

  44. singpolyma

    MattJ: great minds

  45. mathieui

    http://mathieui.net/part/slides-summit28.pdf here’s the slides I had prepared for onion routing, FYI (does not appear to work on the room wifi, but my server is up)

    👀 1
  46. mremond

    There is a XEP about labeling messages

  47. singpolyma

    Just in case anyone is not aware, for onion routing it's worth looking at https://en.wikipedia.org/wiki/Mix_network / mixmaster remailer etc and how that all used to work

  48. nicoco

    > nicoco: Will you be able to fix soon or will it take time? ahem let me try to do that right now, I don't understand anything about the current topic being discussed anyway :)

    😅 1
  49. edhelas

    > There is a XEP about labeling messages Which number ?

  50. singpolyma

    I do like the idea of doing remailing / onion routing sealed sender stuff, but I don't know how we handle multi device here and I think that's the main thing we'd need to think about.

  51. emus

    > I do like the idea of doing remailing / onion routing sealed sender stuff, but I don't know how we handle multi device here and I think that's the main thing we'd need to think about. CC: Daniel

  52. Fishbowler

    mathieui: Slides loaded on my laptop, if they're needed on the big screen

  53. mathieui

    singpolyma, could be done with encrypting to your other devices, in the same message (possibly in another element), and let your server archive that and drop it when forwarding

  54. mathieui

    Fishbowler, thanks, we’ll use it when we get to that topic

  55. singpolyma

    mathieui: yeah, some kind of "write to my archive" operation that doesn't actually send anything

  56. mremond

    > edhelas wrote: > Which number ? It is for security : https://xmpp.org/extensions/xep-0258.html But could be use more largely

  57. singpolyma

    security labels aren't really "label" in the sense of tags

  58. Edwin

    258 is very much only about security labels, and that's nothing to do with tags.

  59. mremond

    Ok, sorry

  60. singpolyma

    SUMMIT: doesn't MLS allow out-of-order within a small window? Last time I looked at libraries there was a setting for how tolerant to be of this kind of thing

  61. Edwin

    mremond: I see how you would think it was similar, because it includes display markers, but there are routing and security implications for any system along the way that is label-aware, so you can't just do anything random, it usually has to agree with configured label catalogs and clearances.

  62. mremond

    Yes, thanks. Indeed, not a good idea to extend the scope, especially for the server that would need to check for extra rules to apply for those messages

  63. Benson

    Wire is advertising MLS implementation

  64. mremond

    https://wire.com/en/messaging-layer-security

  65. mathieui

    at least we know that keeping the 2-days format was a good call, it would have been pretty tight to timebox topics otherwise

    ✔️ 1
  66. singpolyma

    IMO (and I know this is basically what Daniel said IRL) the draw of MLS is that there are and likely will continue to be libraries implementing it. If we ended up "still needing OMEMO" for anything at all it becomes much less interesting very fast

    👍 1
  67. singpolyma

    And forward secrecy protocol is going to be designed to prevent archives :) that's the core purpose. if you have an archive, you've defeated forward secrecy

  68. celeste

    Does anybody know how to spell the name of this 'air' MIMI messenger? Sorry I can't find any information about it online :(

  69. Edwin

    Just Air. I think air.ms is theirs, but that's a placeholder.

  70. Edwin

    I found this at least: https://play.google.com/store/apps/details?id=ms.air&hl=en-US

  71. Daniel

    You can learn more air at fosdem apparently https://mastodon.social/@phoenix_r_d/115983471536996670

  72. Daniel

    You can learn more about air at fosdem apparently https://mastodon.social/@phoenix_r_d/115983471536996670

  73. celeste

    thanks!

  74. Edwin

    https://phnx.im/ is Phoenix R&D GmbH's site.

  75. singpolyma standing ovation for "XMPP is not one thing"

  76. Rémi

    I left the conference, please tell us when you come back 😊

  77. Rémi

    I left the conference, please tell us when you come back 🙂

  78. singpolyma

    nicoco: https://github.com/xsf/xeps/pull/1499

  79. mathieui

    Rémi et al.: we're back into the room

    ❤️ 1
  80. mathieui

    And goffi is starting his lightning talk

    👍 1
  81. Rémi

    SUMMIT: Could the server where the end-user’s account is define what the default policy should be? So, to continue on your example, all firefighters would have a certain default without having to ask each one when they start their client?

  82. Rémi

    SUMMIT: Could the server where the end-user’s account is define what the default scoring algorithm should be? So, to continue on your example, all firefighters would have a certain default without having to ask each one when they start their client?

  83. Rémi

    SUMMIT: Could the server where the end-user’s account is define what the default scoring algorithm should be? So, to continue on your example, all firefighters would have a certain default without having to ask each one when they install their client?

  84. Rémi

    SUMMIT: Could the server where the end-user’s account is define what the default scoring algorithm should be? So, to continue on your example, all firefighters would have a certain default without having to ask each one when they install their client? It wouldn’t be the responsibility of the client developer to decide for litteraly anyone on Earth.

  85. singpolyma

    could, but for most users that just moves it to another entity which doesn't know who they are or what they need

  86. Rémi

    True, but at least that would narrow the user profiles 💁🏻‍♂️ For non-public servers (e.g. companies, hospitals…) that would be a good middle ground IMO

  87. emus

    > SUMMIT: Could the server where the end-user’s account is define what the default scoring algorithm should be? So, to continue on your example, all firefighters would have a certain default without having to ask each one when they install their client? > > It wouldn’t be the responsibility of the client developer to decide for litteraly anyone on Earth. I dont get the first sentence. The semantic confuse me

  88. Rémi

    > True, but at least that would narrow the user profiles > That?

  89. emus

    Could the server where the end-user’s account is define what the default scoring algorithm should be?

  90. emus

    something is wrong in the sentence

  91. emus

    is define?

  92. emus

    definded?

  93. Rémi

    Could the (server where the end-user’s account is) define what the default scoring algorithm should be?

  94. Edwin

    ^ this

  95. emus

    that new sentence misses also a noun after the

  96. emus

    that new sentence misses also a noun after 'the'

  97. Rémi

    Could [the server where the end-user’s account is] define what [the default scoring algorithm] should be? Better?

  98. emus

    > SUMMIT: Could the server where the end-user’s account is define what the default scoring algorithm should be? So, to continue on your example, all firefighters would have a certain default without having to ask each one when they install their client? > > It wouldn’t be the responsibility of the client developer to decide for litteraly anyone on Earth. CC: goffi

  99. emus

    Sorry, my bad

    🤗 1
  100. nicoco

    it's always a bit weird to talk about "the people" as if it were a unified monolithic entity 😬

    💯 2👍 1
  101. goffi

    >> SUMMIT: Could the server where the end-user’s account is define what the default scoring algorithm should be? So, to continue on your example, all firefighters would have a certain default without having to ask each one when they install their client? >> >> It wouldn’t be the responsibility of the client developer to decide for litteraly anyone on Earth. > CC: goffi I'm not sure to get well the question. The score is per-service, not per-user.

  102. singpolyma

    SUMMIT: I like the idea of safety number, but then if we talk about auto-removing no longer used omemo keys won't the safety number change when this happens?

  103. Fishbowler

    Guus's slide: https://docs.google.com/presentation/d/1E1EfbZpJjWrEpsQS3nPZLHZIRysIYTHiXWeT_wZoBEA/edit?usp=sharing

  104. singpolyma

    more docs

  105. debacle

    Off-topic regarding Berlin sprint 2026: Wikimedia wrote again. We get the room again! It will be either 12.-14. or 19.-21. of June. They'll inform me later about the final date. Ignore me.

    👍 1
  106. singpolyma

    specs are cool but need more docs

  107. nicoco

    FWIW in ddg and google, the first thing that pops up for me with "interoperable chat standard" is a blog post from engineering.fb.com "Making messaging interoperability with third parties safe for users in Europe"

  108. egnun

    Summit: In general I think it's imporant to never assume, that the person you are talking to has the same knowledge as you. And in this specific case, that they are basically defining xmpp, couldn't be to our/your advantage? I mean procurement laws prohibit from writing "we want microsoft", so they write, "we want a company to sell us" and then make the paremeters so, that only microsoft products fit the description.

  109. egnun

    (BY the way sorry, if that point made before. It's really hard to type and follow the discussion at the same time)

  110. egnun

    (By the way sorry, if that point made before. It's really hard to type and follow the discussion at the same time)

  111. egnun

    Summit: Why I made the general point. I was at a standards working group meeting. Something about fire protection in buildings. They meet every other year. One of the members of the group (I guess he's an engineer?) , did some "homework", that he was supposed to present to group. What he did, was put some data into a software and he present the result. A number… He got asked. "What does that mean?" He, an engineer, a regular member of that group, literally could not explain, what the significance was.

  112. Benson

    Psi also had Windows and Mac builds, but web clients are also important for desktop.

  113. singpolyma

    yeah. I already point most of my windows customers at my web client even though it's in alpha because it meets their needs best often

  114. singpolyma

    when I get to beta I'll do a tauri thing

  115. Fishbowler

    > specs are cool but need more docs Code is more fun than docs. And I'd rather write docs than a marketing blog post. But maybe this is a marketing problem.

  116. singpolyma

    indeed

  117. edhelas

    https://2024.matrix.org/documents/talk_slides/LAB4%202024-09-20%2011_00%20Julie%20Ripa%20-%20Tchap_%20the%20French%20administration%20federation_%20past_%20present%20and%20future.pdf

  118. edhelas

    https://upload.movim.eu/files/9d94237298995552fa13436420195fbca436dce7/zKiZXbbNmuvt/chat_image.png

  119. nicoco

    > Psi also had Windows and Mac builds, but web clients are also important for desktop. gajim has a .dmg thing for mac os now, and is on the windows store too

  120. mathieui

    (if we talk too much about jabber/xmpp we’ll summon Ge0rG who will suggest zimpy)

    🚀 1
  121. egnun

    "XMPP, pronounce it "ximpy" as in the TV show "Ran and Ximpy" 😉

    🙈 1
  122. edhelas

    Rebranding things with new brands starting with X is always risky :p

  123. Edwin

    Zimpy, avoids the X.

  124. debacle

    celeste, I just stay with "Jabber" no matter what, esp. since I see a lot of "XMMP" and "XMTP" on Mastodon: https://framapiaf.org/@debacle/115978808564597330 I just don't care about the black Cisco van with darkened windows in front of my house.

  125. singpolyma

    the way trademark works they can't "come after you" for most of the ways we as a community use the word anyway

  126. MattJ

    Currently, yes. But if we want to expand the ways we currently use it...

  127. mathieui

    debacle, wait until we leave the summit place before using the word, cisco belgium is not *that* far

    😱 2
  128. singpolyma

    but some people remain scared and always will. which is the problem

  129. singpolyma

    it's not a legal problem. it's a perception problem

  130. debacle

    > (if we talk too much about jabber/xmpp we’ll summon Ge0rG who will suggest zimpy) https://www.urbandictionary.com/define.php?term=zimpy

  131. Edwin

    As a commercial entity, you won't want to use a trademark and/or product name of a competitor.

  132. singpolyma

    not as the name of your company or product, no

  133. singpolyma

    in reference to the network you interoperate with, though, which is how we use it

  134. Edwin

    Marketing a Jabber server or client that doesn't work with Cisco Jabber is only adding to the confusion.

  135. edhelas

    We need Jabber 2.0

  136. Edwin

    Jibber.

  137. edhelas

    J2bber, This time it's serious

  138. singpolyma

    could ask them to affirm the existing license so we're not scared to use this contract we already have? heh

  139. singpolyma

    the main reason they want to bind us to a licensing agreement is that due to non-enforcement in this area the trademark is effectively unrestricted without it

  140. singpolyma

    having an agreement sets boundaries and ground rules, which is a win for them

  141. singpolyma

    I assume that's part of why they did it in the first place

  142. singpolyma

    Video is gone. Who said process one would never use the word Jabber... isn't their flagship XMPP thing named ejabberd?

  143. Edwin

    Fair point :).

  144. debacle

    J in JID and Gajim is also for Jabber, btw.

  145. edhelas

    Gajim as Another Jabber Instant Messenger ?

  146. mathieui

    I would have to rename slixmpp to slibber, which does not sound very good

  147. emus

    > "XMPP, pronounce it "ximpy" as in the TV show "Ran and Ximpy" 😉 Trauma

  148. emus

    Isnt it Stimpy?

  149. Edwin

    And Ren, but that's not important for the joke.

  150. moparisthebest

    relying on the continuing goodwill of a megacorp that doesn't know we exist seems like a bad move

  151. singpolyma

    I do already say "snikket compatible" in some places alongside saying "jabber"

  152. singpolyma

    > relying on the continuing goodwill of a megacorp that doesn't know we exist seems like a bad move it's not good will. it's established law + a contract. but the discussion was about having cisco re-affirm / re-negotiate the contract

  153. mathieui

    moparisthebest, that’s why getting at least one recent statement (or even a promise) would be good to know where they stand

  154. moparisthebest

    1 current employee can say whatever now, doesn't matter, relying on the continuing goodwill of a megacorp that won't remember we exist tommorow seems like a bad move

  155. singpolyma

    contract law isn't goodwill

  156. moparisthebest

    have you looked at the contract?

  157. mathieui

    singpolyma, there is contract law and then there is a megacorp sending an army of lawyers to shut you up

  158. singpolyma

    i was reading it just now

  159. singpolyma

    mathieui: nothing in this world will stop them from sending lawyers if they suddenly want to. no matter what word you use :)

  160. singpolyma

    so on that basis *everything* is goodwill, heh

  161. nicoco

    How about we normalize saying "I'll send you a message via SMTP" instead of "I'll send you an email" so that it's totally fine to keep on saying XMPP? why should *we* change, right? ;)

    😅 1
  162. moparisthebest

    if the current contract is valid, if, it requires the JSF to police use of the trademark, and if they don't, contract void

  163. mathieui

    singpolyma, yes, but then there is prodding the IP of a megacorp and there is just being outside of their field of view

  164. moparisthebest

    Where's xsf's legal team doing this?

  165. singpolyma

    indeed. as I said, setting up ground rules like that is the reason cisco agreed to it in the first place

  166. moparisthebest

    look I agree legally, per fair use, it's probably fine... but most of us don't have the millions required or time to fight cisco in court to prove it, so pick another name

  167. singpolyma

    > Where's xsf's legal team doing this? I think we're effectively dealing with all current misuse (in that there is none)

  168. singpolyma

    if you pick another name you still need the millions to fight. common law trademark is a thing for example ;) they can always come

  169. singpolyma

    what actually matters as mathieui says is if they notice you or care

  170. mathieui

    since we have plenty of xml elements in the protocol, maybe we could rename the protocol to Element

    🤯 1😆 2
  171. singpolyma

    which we have decades to see that so far they don't

  172. moparisthebest

    >> Where's xsf's legal team doing this? > > I think we're effectively dealing with all current misuse (in that there is none) I even agree, but our opinions don't matter, only the opinion of 1 of cisco's army of lawyers who can singlehandedly make our lives hell does

  173. ralphm

    For reference, more information on the Jabber trademark agreement: https://xmpp.org/about/xsf/jabber-trademark/

    👍 1
  174. moparisthebest

    > For reference, more information on the Jabber trademark agreement: https://xmpp.org/about/xsf/jabber-trademark/ and XSF hasn't enforced that in years, which alone is all cisco needs to call the agreement void

  175. singpolyma

    let's do a screenshot of every client and every page load shows you a different one ;)

  176. singpolyma

    moparisthebest: I don't think that's true? XSF is effectively enforcing it

  177. singpolyma

    saying "no one has broken the agreement" is not "no enforcement happened"

  178. moparisthebest

    these are all silly legal arguments though, for me the simplest one is when I search jabber only cisco stuff fills the first page

  179. ralphm

    There have definitely been cases around the trademark that Board has handled over the years. We don't shout about that

    👍 1
  180. singpolyma

    sure. there's a difference between being allowed to use the word in certain ways and wanting to. which is where we started here

  181. goffi

    Can me make a small break after this talk?

    ✔️ 2
  182. moparisthebest

    I don't think anyone is gonna change their opinion on this, i don't want to confuse new users searching, or risk a legal action from cisco, so I'll never say jabber

  183. moparisthebest

    now lets agree to call them XIDs ;) 🧌

  184. ralphm

    moparisthebest, I think that you completely misunderstand the trademark agreement and our role in it. I suggest you read the material I linked.

  185. moparisthebest

    I did, what am I misunderstanding

  186. moparisthebest

    oh that page doesn't have the pdf agreement with cisco which is what i was talking about

  187. egnun

    emus: In regards to the "professional" recommending joining propietary "social" media. Not necessarily. I mean, the FSFE, "Open Source Initiative", OSBA. They all work more or less "in the background" and directly with businesses, lawmakers and administrations.

  188. mremond

    I tend to agree with @celeste that I am now getting used to Zimpy and it could be the name not of a product but of a mascotte (another light bulb form ?) that implementers could reuse ? It may be worth trying to see if people adopt it.

  189. edhelas

    Yay mascots :3

  190. edhelas

    And we can fund Ralph by selling Zimpy teddy bears

  191. celeste

    like i know it:s kind of silly...but already zimpy has a movement......zooom......it's also oddly retro and dorky but in an approachable way. dorkyness, diversity etc.....i am beginning to sound like a marketing person....

  192. edhelas

    Can't wait for the Zimpy cosplay at the XMPP Convention

  193. mathieui

    celeste: congrats, you're now in charge of marketing

  194. edhelas

    Can't wait for the Zimpy cosplays at the XMPP Convention

  195. emus

    > emus: In regards to the "professional" recommending joining propietary "social" media. Not necessarily. > I mean, the FSFE, "Open Source Initiative", OSBA. They all work more or less "in the background" and directly with businesses, lawmakers and administrations. I was responding to those concrete requests (Facebook, Insta...)

  196. ralphm

    moparisthebest, the page I linked has side navigation that will bring you to the right documents. But specifically, we are *not* required to enforce the trademark as if we were the trademark owner.

  197. Rémi

    If you’ve personally proposed investing time or energy on something, please write it yourselves in the Pad (https://pad.nixnet.services/I-8sGqciQjiALG30YE60iA?edit), I didn’t want to make mistakes while not even sure about who was speaking

  198. edhelas

    https://fosdem.org/2026/schedule/event/7XJL9E-engineering_xmpp_federation_building_messaging_voice_social_features_across_inde/

  199. edhelas

    https://fosdem.org/2026/schedule/event/EVSXLA-movim-building-decentralized-social-network-xmpp/

  200. edhelas

    > 📢 Movim: Building a Decentralized Social Network on XMPP > 📍 Room: AW1.126 > 📅 Day: Sunday 1st of February > 🕛 Start: 13:45 > > In this conference we'll discuss the technical challenges of building a rich web frontend on top of XMPP, showcase the exciting features recently added to the project, and introduce the upcoming planned ones.

    👍 1
  201. Edwin

    I assume you will add this to our own wiki page in a moment, so we have all the information in one place so we won't have to look for it everywhere.

  202. edhelas

    Yup, little hands are currently doing it ✨

  203. ralphm

    Also, “[y]ou are not allowed to bring fridges, coffee machines or any electrical appliances like this!”

  204. mathieui

    I’ve added the talks to the wiki page

  205. Edwin

    :)

  206. celeste

    https://compost.party

  207. celeste

    https://archive.is/w78l4

  208. celeste

    it's more online during the summer.....

  209. edhelas

    "Dear Friend, I hope that my <stanza/> has finally arrived, the wind was blowing the past few days and my server..."

    😂 4
  210. mathieui

    edhelas, did you think of https://lists.openstreetmap.org/pipermail/talk-nl/2011-September/013148.html ?

  211. mathieui

    I don’t speak much dutch though

  212. edhelas

    https://www.ffi.no/en/publications-archive/cross-domain-communication-using-an-xmpp-chat-guard

  213. edhelas

    https://www.wizbii.com/company/thales-communications-security-s-a-s/job/stage-bac-5-dveloppement-de-messagerie-instantane-h-f-3

  214. edhelas

    Job offers at Thales looking for people on SIP/XMPP :D

  215. lissine

    fact: Researchers in Antarctica host Prosody for instant messaging

    ❤ 1❤️ 3
  216. lissine

    https://prosody.im/testimonials

    🔬 1
  217. Rémi

    +1 on corridor discussions, that’s partly why I said I prefer in-person

  218. Rémi

    Have to go sorry my coworking is closing, hopefully you’ll still be there in 15 minutes

  219. moparisthebest

    So it's worse than I remembered? https://xmpp.org/docs/Trademark_License_Agreement.pdf these are agreements not between cisco and xsf but between jinc and jsf lol, seems fair to assume lawyers at cisco don't even know these exist It also says jabber can't be used with any commercial project without written permission from JINC. That means jmp/cheogram/ejabberd etc etc aren't allowed to use it right? (per this agreement anyway)

  220. Benson

    Will onion routing slides be posted somewhere online?

  221. moparisthebest

    https://xmpp.org/docs/Trademark_Enforcement_Agreement.pdf is even worse because it clearly expired may 4 2004 right?

  222. zeank

    Ejabberd precedes any of that I think

  223. Ge0rG

    I'm on my way to Brussels, would be cool to get a ping with the location once the dinner plans have been decided upon

  224. emus

    https://mathieui.net/part/slides-summit28.pdf

  225. Benson

    Thanks

  226. jsautret

    > zeank wrote: > Ejabberd precedes any of that I think Yes, ejabberd started the 16th November of 2002

  227. mathieui

    xtls: https://www.ietf.org/archive/id/draft-meyer-xmpp-e2e-encryption-02.html

  228. Rémi

    Thank you for this Summit and for making remote participation possible! See you next time, hopefully in person

    👍 1
  229. Ge0rG

    Are there any dinner plans?

  230. Thilo Molitor

    Daniel, i and Matthew are at the grand placa

  231. mremond

    It was nice getting to see you all ! Enjoy Fosdem !

    ❤️ 2
  232. Fishbowler

    Thanks to everyone who made me so welcome on my first Summit.

    ❤️ 1
  233. Fishbowler

    Thanks to emus for organising, for everyone who did note taking, and to everyone else involved in making a smashing 2 day event.

    👍 1
  234. emus

    Thank you! That was not only on me but also Daniel, Guus & Ralph! Special thanks to Edwin for helping out and you Dan! Thanks for everyone coming and making the even fruitful!

    ❤️ 3
  235. emus

    > Daniel, i and Matthew are at the grand placa Are you still there?

  236. emus

    any other folks I can join?

  237. nicoco

    Neox, mathieui, edhelas and I plan to eat something, did you do that yet? Are you at the beer event?

  238. mathieui

    (If edhelas arrives one day)

  239. emus

    > Neox, mathieui, edhelas and I plan to eat something, did you do that yet? Are you at the beer event? Im leaving my flat now and have done nothing in that regard. I would join

  240. nicoco

    Cool! We meet you in 15, where are you exactly.

  241. edhelas

    I'm there

  242. emus

    Where? ✌️

  243. emus

    edhelas, nicoco:

  244. nicoco

    We are at the centre of grand place

  245. nicoco

    emus: where are you exactly?

  246. emus

    Midi

  247. nicoco

    Oh I thought you were in grand place?!?

  248. nicoco

    Call me xmpp:nicoco@nicoco.fr

    👍 1
  249. emus

    Just a quick call via this mysterious performant protocol. Worked ✔️

  250. Karel

    dwd, you mentioned that you will have some transportation from the NH to the ULB in the morning? Is there still a free spot by any chance? If not, I will come on my own, it's no problem