XSF Discussion - 2018-06-21

> labdsf> flow, what if someone sents silent messages to bare JID?

rfc612(0|1) routing rules apply

and possibly carbons or im-ng routing rules

labdsf, correct

Hi

o/

XSF Board Meeting | Logs: http://logs.xmpp.org/xsf/ | Agenda https://trello.com/b/Dn6IQOu0/board-meetings

0. Welcome and Agenda

Who do we have?

And what do you have?

Here

Here, headache.

Be well, sir.

instant cure: less webrtc

I've been swamped in other stuff, so I know the feeling.

Was there a meeting last week? I was tied up in another (work) meeting.

There wasn't

Oh, on this topic, I contacted Martin a couple of weeks ago

He moved house, job and other stuff, he said he'll be back online as soon as he can

Oh, that's good to hear.

I don't feel we have anything pressing at the moment.

(survey?)

The two items on my radar are the GDPR team and the survey

Ok

Let's start with

1. Survey

I'll take minutes too

(thanks)

Survey is easy... I simply haven't had time to do anything with the results yet

Clear.

I have them in a spreadsheet, but the format is non-trivial to get useful overviews from currently, it needs a bit of processing

Stupid things like it put the ratings as text strings instead of numbers, so it's "(1) Poor" to "(5) Excellent", etc.

Right. Take your time to get that right then.

:-(

and I've just been a bit busy the past couple of weeks

Same here.

But yeah, it's top of my todo, so hopefully by next week we can discuss it

Nothing else to report

Thanks

2. GDPR

Did we get an answer from Alex?

I sent him some messages, but he didn't respond

Did we ask Alex? 🙂

I can ping him again

I also pinged Winfried, who said his time is limited but he'd be happy to help where he can

awesome

Cool.

I don't think we will have that much to do, I'm willing to take on the iteam part of things, for the most part

Right, probably mostly making the inventory itself

so I see the two steps as 1) inventory of data 2) analysis of what actions we need to take for each of those

And the Privacy Policy

and that

ok

3. AOB

None here

nor here

I'll be awol for two weeks, starting july 13th.

So that brings us into

4. Date of Next

+1w works for me.

I'm sure there will be other vacation plans. I'm just going to keep assuming a meeting every week and see if we get quorum

+1W it is

5. Close

Thanks all!

thank you!

back to me MediaTrackConstraints 😞

XSF Discussion | Logs: http://logs.xmpp.org/xsf/ | Agenda https://trello.com/b/Dn6IQOu0/board-meetings

Thanks

Guus: good luck with that

(and the headache)

tx

more coffee.

I'm just dropping this link here again as it might interest you https://nl.movim.eu/?about#caps_widget_tab it's some clients statistics generated from the presences that I've cached

Nice!

edhelas: what's the user base for that? Users on movim.eu or also remote servers.

yeah on this nl.movim.eu pod, so I'm not expecting to have 5% of Movim clients worldwide

also Movim users (and their related JIDs) are close to the XMPP community as well so aware of "modern clients"

Is this over the total number of presences? Or total number of full jids?

but it's basically compiled from all the full jid yes (they are merged across the connected accounts as well, see https://github.com/movim/movim/blob/master/app/widgets/Caps/Caps.php#L68)

https://keybase.io/blog/keybase-exploding-messages https://keybase.io/docs/crypto/ephemeral (one more messenger implements ephemeral messages)

> The goal is that even if an attacker steals one of your encrypted exploding messages from our server, and then later steals one of your devices and all the keys on it, there should still be no way for the attacker to decrypt the message.

By the way, it seems all these messengers (signal, keybase, wire) expose user device list to contacts, probably because it is way easier to manage keys this way. Somewhat related to recent MIX discussion: trying to hide multiple devices behind a pseudonym limits interaction to simple chat. File transfers, calls, etc. rely on direct interaction anyway.

> I'm just dropping this link here again as it might interest you https://nl.movim.eu/?about#caps_widget_tab it's some clients statistics generated from the presences that I've cached "Conversations" is listed twice, 50% and 2.3%