XMPP Summit - 2019-02-01


  1. Ge0rG

    Good morning. Did everyone have a great party last night, or is Summit resuming the tech talks? :D

  2. Seve/SouL

    :D

  3. pep.

    !

  4. jjrh

    Beh train stopped

  5. mathieui

    everyone had a great snow-delayed train to diegem

  6. jjrh

    The one time on this trip I leave to make it exactly on time and not early is the day there is a delay

  7. MattJ

    jjrh, I think our train passed it on the way :)

  8. jjrh

    Booo

  9. jjrh

    Almost there now

  10. alameyo

    i have 20 mina to next train :(

  11. pep.

    Pad is still at https://etherpad.wikimedia.org/p/XMPP_Summit_2019_Day1 today!

  12. Tobias

    yeah...let's use that

  13. Tobias

    also, I'd be nice if there was more contribution on the minutes

  14. mathieui

    Ge0rG, we’re starting

  15. Tobias

    anyone needing A/V

  16. Tobias

    ?

  17. jonas’

    I can’t attend remotely this time

  18. jonas’

    but Ge0rG might want to listen in?

  19. Zash

    pep. talks about Moved

  20. Seve/SouL

    Honestly it would be cool to at least being able to listen the discussion (maybe for next year), because I could listen to it but not participate

  21. Guus

    SouL, i think you _can_ listen today

  22. Guus

    or at least, it is technically possible for us to provide you with a stream.

  23. ralphm

    Daniel: https://xmpp.org/extensions/xep-0068.html#approach-fieldnames

  24. Zash

    https://xmpp.org/extensions/xep-0077.html#usecases-cancel https://xmpp.org/extensions/xep-0077.html#example-16

  25. Link Mauve

    Hey, you are editing the pad both at the bottom and at the top.

  26. mathieui

    I did at the top since Tobias added day2 at the top

  27. Tobias

    i thought reading it top to bottom, folks would notice it :)

  28. Ge0rG

    I left my earpiece at home, so I can't listen in without offending the cow-orkers

  29. pep.

    Ge0rG, takeaways for <moved/> is, "offline servers" support as a separate XEP, not in the scope of our first draft. I think it's reasonable. We can still support scheduled shutdowns

  30. Ge0rG

    pep.: any insights on the best protocol to use for embedding <moved/>? PEP? Messages? Presence? All of the above?

  31. Ge0rG

    I've heard there are unmaintained servers without persistent PEP

  32. Ge0rG

    Oh, also PEP access model: public --> potential for spam; roster --> your contacts lose access once one of the clients has completed the "moved" game

  33. pep.

    <error type='cancel'><gone/></error>

  34. pep.

    And we'd have a mechanism (IBR?) to be able to set the tombstone on your account

  35. pep.

    So the old server can even only send that gone error to your contacts

  36. Ge0rG

    so this won't work on today's unmaintained servers, but only on tomorrow's ones, which support moved?

  37. pep.

    Indeed. But as you said that doesn't work on today's server without persistent PEP

  38. jonas’

    today’s servers have persistent pep

  39. jonas’

    (mostly)

  40. Ge0rG

    pep.: backward compatibility is the toughest piece of any protocol

  41. Ge0rG

    jonas’: you might be biased by only looking at the *popular* servers.

  42. pep.

    Ge0rG, ok, so I still don't know how to answer that.

  43. pep.

    And I guess you don't either

  44. pep.

    I guess we can have both PEP and <gone/> tbh

  45. Ge0rG

    pep.: maybe a <message><moved> to all contacts in addition?

  46. Zash

    <message to=everyone type=chat><moved to="newjid"/><body>Hey, I'm moving to a new account, please add me there: newjid</body></message>

  47. pep.

    yeah backwards compatibility through natural languages in <body/>

  48. Ge0rG

    Zash: https://op-co.de/tmp/xep-0283.html#message

  49. Ge0rG

    pep.: ^

  50. Zash

    Ge0rG: Exactly :)

  51. Ge0rG

    > The <body/> MUST NOT contain information unrelated to the account move. This allows a receiving client that understands the <moved/> element to discard the <body/> and use an appropriate internal presentation format.

  52. pep.

    heh, TIL of that document

  53. Ge0rG

    pep.: ouch. sorry. Should have mentioned that earlier.

  54. Ge0rG

    I've stopped short of introducing PEP

  55. Ge0rG

    It's not even git-commited yet, just a stash in my $HOME

  56. Zash

    Delay tags can/are scoped by the delaying entity

  57. edhelas

    hello people

  58. edhelas

    sorry to ask again, what is the url of the webex meeting already ?

  59. jonas’

    edhelas, https://cs.co/rudy maybe?

  60. jonas’

    I don’t know for sure, I’m not listening in today

  61. Ge0rG

    yes, https://cs.co/rudy works

  62. Ge0rG

    it even had an XML snapshot slide a bit back

  63. edhelas

    okay :) I'm in, but no video

  64. edhelas

    let's try on chrome

  65. Ge0rG

    edhelas: there is no video, AFAICS

  66. edhelas

    oh ok

  67. Ge0rG

    but maybe there is and my firefox is too old

  68. ralphm

    Huh? Three is

  69. ralphm

    There

  70. edhelas

    tried with chrome/firefox, no video

  71. ralphm

    Weird

  72. edhelas

    oh actually I have the video stream of goffi now :)

  73. edhelas

    so it's definitly an issue with the cameras in the room

  74. MattJ

    Kev, room in the schedule for a very brief demo from me?

  75. edhelas

    if there's still room left I can also do a demo :p

  76. edhelas

    would it be possible to list Moya on the XMPP website ?

  77. MattJ

    edhelas, I think you can submit a PR

  78. MattJ

    or Daniel :)

  79. Daniel

    i'm just a consultant/contractor for Moya. I don’t have decision power

  80. edhelas

    can you share the screen ?

  81. Daniel

    oh never mind. i missunderstood that question

  82. pep.

    edhelas, it's supposed to be

  83. Ge0rG

    I can't see anything.

  84. pep.

    ralphm, ^

  85. Ge0rG

    audio works, but no video/screen sharing

  86. MattJ

    Ge0rG, https://jmp.chat/

  87. Ge0rG

    MattJ: I never completed their onboarding, so I wanted to see it in action at least remotely.

  88. Ge0rG

    Daniel's presentation worked.

  89. edhelas

    yes I can confirm, like Ge0rG

  90. ossguy

    https://gitlab.com/ossguy/sgx-catapult

  91. Ge0rG

    ossguy: do you happen to have a video of what you've shown right now?

  92. ossguy

    yes, I did a similar demo at DebConf that was recorded - let me get you the link a minute...

  93. ossguy

    Ge0rG: it starts at 29:40 in https://saimei.ftp.acc.umu.se/pub/debian-meetings/2017/debconf17/live-demos.vp8.webm

  94. ossguy

    (not sure if there's an easy way to add that time offset as a # thing in the URL)

  95. Ge0rG

    ossguy: thanks, I'll watch it when I'm off my metered mobile connection.

  96. ossguy

    you're very welcome

  97. Ge0rG

    VIDEO!!!1!

  98. edhelas

    VIDEO §§§

  99. edhelas

    annndd it's gone

  100. mathieui

    blame Link Mauve

  101. Ge0rG

    Whatever you guys did, do it again please.

  102. edhelas

    the video only turns on when Link Mauve is filmed

  103. Zash

    works now?

  104. mathieui

    note how he made his "slides" in tmux tabs

  105. Ge0rG

    We had Link Mauve's screen, then Link Mauve's face, and now it's gone again

  106. edhelas

    > Video is not currently available due to low bandwidth or local computer conditions (such as CPU or RAM use). Video will resume automatically when conditions improve.

  107. Ge0rG

    no video any more

  108. edhelas

    I'm sure I have the bandwidth for it

  109. mathieui

    edhelas, rust is too powerful for your computer

  110. Zash

    "worksforme" / ralphm

  111. pep.

    https://gitlab.com/xmpp-rs/xmpp-parsers/

  112. edhelas

    mathieui :(

  113. jjrh

    https://wiki.xmpp.org/web/Summit_23#Show-and-tell has some of the links

  114. ralphm

    Sorry people, I don't know why it (sometimes?) doesn't work for you, but I've been constantly connected to the stream on my laptop, too, and see no issues there.

  115. edhelas

    ralphm you're stealling all our bandwidth !

  116. Ge0rG

    There is *at least* one writer thread *cough*cough*

  117. edhelas

    XEP-xxxx: Sextoys over XMPP

  118. Zash

    Relevant https://media.ccc.de/v/35c3-9523-internet_of_dongs

  119. edhelas

    I'm actually curious to know more about this integration in sextoys, they actually have a chip that can talk XMPP inside the object ?

  120. mathieui

    edhelas, probably inside a smartphone app

  121. mathieui

    Zash, that talk was quite disappointing

  122. intosi

    At one EuroOSCON many moons ago, we had a lengthy chat with someone using (amonst other open tech) XMPP for teledildonics.

  123. edhelas

    and bluetooth on the other end

  124. goffi

    or inside a body

  125. edhelas

    soon pacemakers powered by XMPP, better not miss a stanza there

  126. ralphm

    edhelas: possibly related too: https://xmpp.org/extensions/xep-0132.html

  127. mathieui

    poezio connection code inside pacemakers

  128. pep.

    please no

  129. pep.

    *reconnecting* *reconnecting* *reconnecting* *oops*

  130. intosi

    ralphm: that XEP even uses <gone/> ;)

  131. ralphm

    https://ralphm.net/publications/xmpp_chat_voip

  132. mathieui

    (don’t forget to edit your presentation description in minutes if you think it doesn’t do you justice)

  133. MattJ

    https://matthewwild.co.uk/projects/scansion/

  134. flow

    https://geekplace.eu/box/XmppNioTcpConnectionStateGraph-aQPiEKBwNk8pZK5V1lb5uYFjozeJfI.png

  135. edhelas

    that's a nice flow

  136. flow

    TIL teledildonics

  137. Seve/SouL

    +1

  138. jonas’

    what?

  139. jonas’

    -vv

  140. Seve/SouL

    Same here

  141. flow

    jonas’: 12:23:09 intosi> At one EuroOSCON many moons ago, we had a lengthy chat with someone using (amonst other open tech) XMPP for teledildonics.

  142. Zash

    Ge0rG: Anything to say about xmpp developer foundation or somesuch?

  143. Daniel

    https://xmpp-developers.foundation/about/

  144. Ge0rG

    Zash: I'm not the right person for that. But I've heard somebody wanted to found a JSF

  145. Zash

    Ge0rG: JSF vs XDF - FIGHT!

  146. flow

    why does it always have to be a vs. and not simply live and let live ;)

  147. vanitasvitae

    flow: its about the name

  148. flow

    vanitasvitae, ahh, if this is the biggest issue, i am sure we can find something everyone is unhappy with

  149. debacle

    For everybody interested in IoT, please remember, that there is a MUC, that needs more participants and more discussion: xmpp:iot@muc.xmpp.org?join

  150. Seve/SouL

    Zimpy

  151. vanitasvitae

    Lets name the developer foundation matrix.org

  152. jonas’

    flow, I’m also sure we can come up with an acronym with is massively misleading

  153. jonas’

    ah, vanitasvitae did it already

  154. vanitasvitae

    You're welcome :)

  155. jonas’

    Massive Advancement Towards Rapid Integration of XMPP

  156. jonas’

    or something

  157. vanitasvitae

    Perfect!

  158. vanitasvitae

    Spld

  159. vanitasvitae

    *sold

  160. mathieui

    jonas’, Massive Advancement Towards Rapid Integration of XMPP. Openly Regulated Guidelines

  161. debacle

    s/Integr/Implement/ ?

  162. jonas’

    debacle, !

  163. edhelas

    Planner Jabber is actually available on XMPP Pubsub https://nl.movim.eu/?node/news.movim.eu/PlanetJabber :) #eatyourownfood

  164. Ge0rG

    jonas’: I thought MATRIX is Monolithic Awfully Trendy Re-Invention of XMPP (courtesy of debacle)

  165. jonas’

    that’s the other Matrix

  166. vanitasvitae

    Sprint XYZ - presented by the XSF and XDF!

  167. Ge0rG

    Speaking of marketing... "We bring the Pee into XMPP"

  168. flow

    "Monolithic Awfully Trendy Re-Invention of XMPP" ← love it

  169. vanitasvitae

    Re planetjabber: it still contains philosophy posts

  170. mathieui

    Ge0rG, please stay away from public relations in any form

  171. Zash

    https://www.ag-software.net/matrix-xmpp-sdk/ this Matrix?

  172. pep.

    That's the channel we've been idling in fwiw, xmpp:jsf@chat.cluxia.eu?join - jsf is probably not the name, and xdf came afterwards.

  173. Ge0rG

    there is precedent for a Jabber®-named organization, and there is precedent for the JSF

  174. Ge0rG

    And if we keep to the notion of "Jabber" being the federated IM network, a JSF kinda makes sense

  175. singpolyma

    Merry Band of Jabberers

  176. Zash

    pep.: look up

  177. vanitasvitae

    Just do a poll regarding the name

  178. vanitasvitae

    There is a xep for that, right?

  179. Ge0rG

    Link Mauve is very quiet on the audio stream

  180. Ge0rG

    There is also an ongoing effort to report spam-forwarding IBR servers to the admins and to the respective ISPs, to get them shut down

  181. Ge0rG

    https://op-co.de:5281/upload/FPEZZRp7HmMoJXWQ/Screenshot_20180312-121844.png

  182. flow

    Ge0rG has maaaany friends

  183. Ge0rG

    but they all only speak Russian :(

  184. flow

    Ge0rG, I thought you too (at least a bit)?

  185. ralphm

    vanitasvitae: as I said, Planet Jabber is about People Doing Jabber/XMPP stuff. It is not about Posts About Jabber/XMPP.

  186. flow

    ralphm, I think there is maybe a desire to change that

  187. Ge0rG

    99.9% of current spam can be blocked by some easy heuristics and blocking of URLs from non-subscribers

  188. ralphm

    flow: there's also Planet Jabber News which includes software update feeds

  189. Ge0rG

    if the audio wasn't so bad, I'd contribute some insights too

  190. Ge0rG

    Maybe we can pay the spammers *more* to not send any spam any more! 😁

  191. Seve/SouL

    :)

  192. Zash

    What could go wrong

  193. Ge0rG

    Zash: Cobras

  194. pep.

    We need to hire a hitman

  195. Seve/SouL

    Thanks for explaining MattJ

  196. flow

    Hmm, the discussion is dereailed it appears, was interersting to hear what Link Mauve explained, but right now I don't know where we are heading to

  197. pep.

    Spammers might be listening in this room, we need not to reveal our secrets

  198. Ge0rG

    *raise hand* my spam solution isn't blocking all messages from foreigners

  199. Tobias

    Ge0rG, alright...will proxy it

  200. Daniel

    flow, i think a lot of people don’t know how spammers or spim work. so getting everyone on the same page (ie how does the threat vector look like exactly) is certainly valuable

  201. dwd

    pep. Good point. Maybe we should lay some false trails. How about I suggest that the spammers are easy to spot because they use plaintext whereas everyone else uses XHTML-IM?

  202. Tobias

    Ge0rG, Link Mauve is explaining things in more detail

  203. Ge0rG

    Tobias: Link Mauve is very quiet, so I'm missing out random fragments

  204. pep.

    dwd, sounds good to me

  205. flow

    Daniel, true, but given the limited time I think it would be benficial to focus on what actually works regarding spam prevention

  206. Ge0rG raises hand

  207. dwd

    pep., Maybe a XEP that has a new element: <this-is-not-a-spam xmlns='urn:xmpp:spam:0'/> that we pretend we check for?

  208. Tobias

    Ge0rG, next time i'll bring a megaphone

  209. Daniel

    right. but to work out the solutions it is importants to understand how the problem actually looks like

  210. flow

    Ge0rG, you need to tell Tobias to raise his hand for you :->

  211. Daniel

    for example the information that there are only ~3 spamming services is interesting

  212. Tobias

    Ge0rG, it's up

  213. Daniel

    also the information that spammers can read

  214. Daniel

    which apparently people weren’t aware of

  215. Tobias

    Ge0rG, are you on audio? if not just write what you want proxied

  216. Ge0rG

    Tobias: I'm on audio, just need to unmute myself and surprise you all with my voice

  217. Tobias

    alright

  218. intosi

    We could ask spimmers to use https://xmpp.org/extensions/xep-0076.html

  219. Ge0rG

    https://github.com/JabberSPAM/blacklist re what Link Mauve is saying

  220. Tobias

    Ge0rG, PING

  221. Seve/SouL

    Yes Ge0rG

  222. flow

    So according to https://github.com/JabberSPAM/blacklist/blob/master/blacklist.txt, the current size of the problematic services is 1

  223. flow

    Doesn't look so bad

  224. Guus

    😛

  225. Daniel

    flow, there is a due processes to get on that list and off that list

  226. Daniel

    quite a few servers are about to get on that list

  227. pep.

    (which is what the document explains)

  228. Daniel

    it just hasn’t happened yet

  229. flow

    ahh, ok

  230. Ge0rG

    messages bots domain ---------- ---------- ------------------------------------ 4307 3171 bunkertor.org 1984 628 jabber.cd 1950 1169 paranoid.scarab.name 1351 1044 darkengine.biz 1233 364 amtserver.com 1064 254 anyproxy.net 1061 251 securejabber.me 837 479 unstable.nl 771 258 biniou.net 676 267 default.rs

  231. Daniel

    but they are close to being escalated

  232. Guus

    of my last 10 spam messages, 2 are on this list.

  233. jonas’

    if Ge0rG isn’t DoS’d out of the internet first

  234. pep.

    jonas’, too late?

  235. mathieui

    thanks Guus

  236. mathieui

    Ge0rG*

  237. intosi

    I've seen spam from domains on this list as well.

  238. mathieui

    (but thanks Guus for summit organization anyway I guess)

  239. Guus

    You're welcome 🙂

  240. Ge0rG

    Some clients will block incoming messages/subscription requests until a captcha is solved

  241. Ge0rG

    Like https://github.com/redsolution/xabber-android/issues/851

  242. Tobias

    In case people remember stuff from the spam discussion that's missing on https://etherpad.wikimedia.org/p/XMPP_Summit_2019_Day1 , please add it

  243. Ge0rG

    With the current level of sophistication of the spammers, there is NO NEED for captchas

  244. intosi

    Ge0rG: interesting observation.

  245. Ge0rG

    Tobias: *raises hand* sometimes spam accounts are created, then not logging in for multiple weeks, then wake up and spam

  246. Daniel

    yes.

  247. mathieui

    often, yes

  248. Daniel

    but i don’t think it matters to the pattern of suddenly sending messages to 1000s of people

  249. Tobias

    Ge0rG, it's up

  250. mathieui

    +1

  251. Daniel

    that pattern should be blocked regardless of how old the account is

  252. Ge0rG

    less-than-secret example from the firewall: ``` # outgoing messages to non-contacts need to be full-body-searched. KIND: message TYPE: chat|normal|headline NOT SUBSCRIBED? JUMP_CHAIN=user/bodycheck ```

  253. Ge0rG

    from a fast skim of the rules, the only thing that's not coming from the message is the mutual subscription status

  254. Tobias

    maybe the Rspamd protocol documentation can also provide some helpful input

  255. singpolyma

    so the antispam server doesn't need the whole roster, just a boolean basically about the relationship between from and to

  256. Zash

    none/to/from/both

  257. Tobias

    maybe the Rspamd protocol documentation can also provide some helpful input https://www.rspamd.com/doc/architecture/protocol.html

  258. Ge0rG

    Zash: the relevant question is: did the recipient authorize the sender before

  259. singpolyma

    would the blacklist being public be as problematic as the rules? I would think probably not?

  260. Ge0rG

    singpolyma: the blacklist doesn't contain any black magic.

  261. mathieui

    yet.

  262. Ge0rG

    There are various public blacklists already

  263. flow

    Ge0rG, that sounds like it could be feasiable to just put additional metainformation in the message send to the spam indendification service, versus the spam identification service asking for additional information from the xmpp server

  264. Ge0rG

    I've only created my own one because none of the earlier ones had a due process

  265. Ge0rG

    flow: yes.

  266. Ge0rG

    flow: just a metadata flag

  267. singpolyma

    for sure. due process is a good thing that can help us from becoming like email

  268. Ge0rG

    singpolyma: I wanted to be a _good_ RBL

  269. flow

    Ge0rG, question is, will there be more metadata in the future? Probably, but then we question is "How much?"

  270. Seve/SouL

    Did I hear correctly :)

  271. Ge0rG

    Tobias: jonas’ provided measurements from compression with different flushing aggressivity

  272. Zash

    https://blog.thijsalkema.de/blog/2014/08/07/https-attacks-and-xmpp-2-crime-and-breach/

  273. Ge0rG

    jonas’' data on XMPP compression: https://github.com/horazont/aioxmpp/issues/249

  274. Ge0rG

    aioxmpp test suite, sync_flush only (XEP-0138 as written): 40% rx, 20% tx aioxmpp test suite, full_flush after each stanza: 25% rx, 20% tx JabberCat startup (lots of mucs, lots of avatars), full flush after each stanza: 25% rx, 12% tx JabberCat startup (lots of mucs, lots of avatars), sync flush: 36% rx, 12% tx

  275. Ge0rG

    (the percentage being the ratio of bytes saved; tx is from client to server, rx is from server to client)

  276. singpolyma

    so even full flush after every staza could be worth it *if* that is safe in your context

  277. winfried

    EXI!

  278. Ge0rG

    you save 20% of traffic, but add some proper CPU load

  279. Ge0rG

    also RAM

  280. singpolyma

    for sure

  281. Zash

    something something ROI

  282. mathieui

    Ge0rG, which might be something of interest using a smartphone over an edge channel

  283. Zash

    As a server dev, I'm happy avoding the additional memory usage of compression

  284. Ge0rG raises hand: an approach that's maybe worth exploring is a pre-created "official" compression dictionary, containing all the relevant stanzas and namespaces. like http/brotli

  285. Ge0rG

    Tobias: ^

  286. singpolyma

    winfried: is there data on EXI vs compression similar to those numbers above?

  287. Ge0rG

    damn, toolate

  288. Tobias

    Ge0rG, sorry. we moved to the next item

  289. debacle

    Ge0rG in some cases compression actually reduces CPU load, because there is less data to TLS encrypt

  290. Ge0rG

    debacle: I know

  291. Ge0rG

    Is there somebody good at painting? We still need XMPP Compliance Badges

  292. winfried

    singpolyma: some years ago there were some japanese guys, who did metrics on EXI, it worked quite well

  293. Seve/SouL

    Yes! A lot of people!

  294. Seve/SouL

    Somebody writing that donw? Just to know what can we improve in the future for Summits and so on

  295. dwd

    Kev's writing this stuff down, yes.

  296. Ge0rG

    I wish for a working A/V and *especially* better audio, and it would be great if it would work over XMPP

  297. Tobias

    Seve/SouL, see etherpad

  298. alameyo

    https://ctftime.org/writeup/12913 here is kind of compression oracle attack - it was created as hacking challenge but you can get the idea

  299. Seve/SouL

    He has a point though :)

  300. dwd

    Seve/SouL, Who?

  301. Ge0rG

    Video worked and broke down synchronously for me and edhelas, so it must be on Cisco's end

  302. Seve/SouL

    dwd, working on the agenda before Summit (I don't know him unfortunately)

  303. Tobias

    what's at the top of the board?

  304. Zash

    "agenda before reading"

  305. MattJ

    Looks like "AGENDA FUR BY REAPING"

  306. Zash

    for?

  307. Tobias

    something in between i bet,...ta

  308. Zash

    Having the agenda prior to the summit so you can read up on XEPs and whatnot

  309. MattJ

    Ah

  310. Seve/SouL

    I had that experience last year, couldn't have maybe an exact opinion on something

  311. dwd

    That was suggested by Piotr of Erlang Solutions.

  312. Seve/SouL

    Ah I see, thanks dwd

  313. Seve/SouL

    What did happen to think about this information for new people attending?

  314. Zash

    Seve/SouL: What do you mean?

  315. Seve/SouL

    Zash, just curious about if this topic popped up because somebody did something wrong by mistake... Or something like that (Writing how the Summit works, I mean.) Anyway, I may have understood it in a different way, audio is ok but of course not real life.

  316. Zash

    Seve/SouL: No, we want to remember what was done well, so it's not forgotten and can repeated next year

  317. Seve/SouL

    Ok perfect, great

  318. Seve/SouL

    Thank you Zash

  319. Zash

    Seve/SouL: Assuming I understood your question

  320. flow

    Secretary: Add ProtoXEP SEX to the XSF Summit 2020 agenda

  321. flow

    Secretary: Vote for "ProtoXEP SEX" as agenda item

  322. Zash

    /invite Secretary

  323. flow

    Secretary: Add XEP-1234 as recommended read for the "ProtoXEP SEX" agenda item

  324. kingu

    What is he selling?

  325. alameyo

    so anyone, any plans for the rest of the evening?

  326. Seve/SouL

    A more open

  327. Seve/SouL

    .

  328. Zash

    Plans?

  329. Link Mauve

    ArchLinux food!

  330. alameyo66

    Zash: I would do something

  331. Zash

    Do something? After two days of meeting?

  332. pep.

    ArchLinux food!

  333. alameyo66

    so far I am improvising, that's the way to do things too

  334. jjrh

    I'm up for food or drinks if people are meeting somewhere

  335. alameyo66

    jjrh: I am at some street, let me figure out which one

  336. alameyo66

    Lat 50.84829 Lon 4.35174

  337. goffi

    is there anybody going to delirium tonight?

  338. alameyo66

    goffi: I intend that but a bit later

  339. goffi

    alameyo66: yeah not now, I'm working on my talks anyway, won't go before 20:00 at best.

  340. jjrh

    What's delirium?

  341. goffi

    jjrh: delirium café, where's the opening night is happening

  342. Seve/SouL

    Never been there but I have heard that is quite full

  343. goffi

    yes it is

  344. goffi

    I don't plan to stay long, but 2 or 3 beers would be nice

  345. jjrh

    Damn 3000 beers to choose from

  346. goffi

    welcome to Belgium ;)

  347. alameyo66

    I am at the quartier du centre

  348. MattJ

    BTW if anyone is missing a (big) Thinkpad charger, we found one in the Thon hotel lobby and left it at the reception

  349. mathieui

    not me but I could always do with one more

  350. Tobias

    https://wiki.xmpp.org/web/Minutes_of_the_2019_Summit:_Day_two

  351. MattJ

    Thanks!

  352. MattJ

    Oh wow, you typed up all the retro + action items too, I was going to do that... so double thanks :)

  353. Kev

    👍

  354. Tobias

    "Your personal Google+ account is going away on April 2, 2019" oh no. Life will never be the same again.

  355. Zash

    .

  356. Zash

    Did anyone do a headcount?

  357. Zash

    jonas’: (Re compression) You didn't try the "flush when the to/from attr changes" approach to compression?

  358. Zash

    Felt like there were more than 30 people at peak, but maybe that was just the room layout

  359. ralphm

    dwd: lovely small square clean antique red flowery Dutch wooden storage box

  360. Zash

    Oh no, the minutes pad has an infinite loop

  361. Zash

    ralphm: correct horse battery staple?

  362. ralphm

    Discussion on the order of adjectives

  363. Zash

    Ah yes, that's got some specific order

  364. Holger

    goffi: We're there right now.

  365. Guus

    Zash did you just share your password? 😱