XSF Discussion - 2019-12-10

pep.: The repository has been archived several years ago. We have already talked to add the code in /xsf/ GitHub.

Neustradamus, then open an issue asking for this instead?

"The XSF memberbot source code is always missing" what does that even mean

The ticket is here, you have closed it ;)

"Could somebody fork the original memberbot repo under the xsf umbrella?" < here take it, that's for you

(read: you can open an issue with this)

Only for you: "The XSF memberbot source code is always missing (in this XSF GitHub)"

Yes I have already forked for a solution about the next ticket, I wait XSF repository to create a PR.

And it is already sent to Alex for a test.

GSoC 2020 has been announced! We want in?

Zash, Yes, I think Bind2 could be done within SASL2. But equally, I see no reason to change the semantics of Bind in order to get the syntax.

dwd: I've been thinking about per device passwords, passing some device id early would help there

Zash: isn't it sufficient to have the per-device-password as a device id?

Ge0rG: Can't do some SASL mechanisms without knowing what to test against first

Zash: no way to test against all?

With SCRAM? I didn't see how

have a shared salt on all passwords?

Yikes.

I'm the last one to oppose a working per-device-password mechanism, just asking questions

Zash, Per-device passwords should be easy enough unless you want to use an existing SASL mechanism.

Or hijack authzid

dwd: with the advent of new SASL mechanisms in the last decade of XMPP, there might be a slight incentive to make it work with the existing ones

I get the pragmatic concerns, but mutilating stuff isn't going to make me any happier.

dwd: I didn't notice the moment when the goal of protocol design became to make you happier ;)

:)

Ge0rG, That moment was the Council election results. ;)

> I get the pragmatic concerns, but mutilating stuff isn't going to make me any happier. T-Shirt waiting to happen

too much text for a t-shirt :(

GSoC 2020's been announced, applications in January, in case no-one's mentioned it yet.

Yeah, Guus did

Fab. About 4 weeks until applications.

anyome from Jitsi Meet (the software and the service) here?

we’re looking for audio/video conferencing with call-in at work, and webex was discarded because it’s too unstable

I don't think anyone from that team is here, but they generally aren't hard to get hold of

poke saghul on twitter, he's quite responsive

what’s twitter?

Nobody knows

jonas’ I've dabbled with it about a year ago.

They're also pretty responsive on their community discourse website thingy

and lastly, there's a community video conference every other week on Monday

Still it's the most annoying way to spread news. I usually have to reload three times to make it show the content.

They really bully you if you have no account and twitter client.

!XSF_Martin: you know about nitter.net

I do, but people keep posting Zwitter links instead of nitter links.

I didn't know about that and now I'm mad you didn't tell me earlier Ge0rG

it actually loads on my phone reliably, unlike twitter...

It's easy to change while posting but it's not easy to change a received link as copypasta to browser and edit is annoying. The person posting should edit it instead of expecting every receiver to fix it on his own. ✏

I just installed an extension https://addons.mozilla.org/en-US/firefox/addon/invidition/

works on firefox desktop and mobile

jonas’, Ge0rG, dwd: So much text! :S

Zash, I’m sorry, but I hope it’s worth it.

This reminds me of The Story of <img>. TL;DR: He who writes the code controls the defacto standards.

Oh dear more text while I was reading that text?

just two lines, one of them being a URL

(from me anyways)

Thank glob, those last two were short 🙂

> TL;DR: He who writes the code controls the defacto standards. Is this a good thing or a bad thing?

Or just a thing

Mostly a thing. Sometimes it causes pain later.

Especially if it's some quick hack that gets too popular to replace, which seems to happen a bit too often for my taste.

hey guys, everyone ready for a member meeting?

today?

now!

!!!

indeed, fun

yes, today and now ;-)

I’ll be partly AFK ✏

here is our agenda for today: https://wiki.xmpp.org/web/Meeting-Minutes-2019-12-10#Call_for_Quorum

Oh, I just voted two hours ago

1) Call for Quorum

as you can see 28 members voted via memberbot. So we have a quorum

2) Items Subject to a Vote

New and Returning members, you can see all applicants here: https://wiki.xmpp.org/web/Membership_Applications_Q4_2019

3) Opportunity for XSF Members to Vote in the Meeting

here, haven't voted yet

anyone here who has not voted yet and wants to do so?

larma, go for it

memberbot is still online

I'll be voting too now

go go go ;-)

Alex, Just add yes for all

larma, can you vote via bot? makes it easier for me

have Winfrieds vote now

Alex, will do

👍

larma, got your vote as well

more last minute voters?

otherwise I will start working on the results and shutdown memberbot

ok, start counting with my 10 fingers now

4) Announcement of Voting Results

when you reload the page at: https://wiki.xmpp.org/web/Meeting-Minutes-2019-12-10#Announcement_of_Voting_Results you can see the results

all Reappliers are accepted. Congrats to everyone

and thanks Alex!

Thanks Alex!

5) Any Other Business?

none from me

congrats to everyone, and thanks to Alex

6) Formal Adjournment

I motion that we adjourn

Seconded

Thirded

thanks everone ;-)

Thanks Alex!

Always curious about the "no" votes. I'm happy to hear comments here or in private if anybody has feedback :)

Awesome! No need to change the council!

XEP-0030 has this sentence: > The value of the 'node' attribute MUST NOT be null. What does this even mean in XML?

very good question

An _attribute_ that's null? 🤔

I'm guessing an attribute that's defined without a value?

that’s not a thing in XML

at least libxml2 won’t parse it

<element att="" />

that’s an attribute with an empty value

not null

True, but that's my best guess at what's ment

I think we had a discussion about the difference between <item node=""> and <item>

Can we please stop living in a Maybe monad :( ✏

pep., maybe.

.

(scnr)

https://search.jabber.network/search?q=muc.xmpp.org

huh

looks like my prosody was in questionable states

maybe it was THE s2s bug

What's with the THE bugs?

(ftr, the link did not show any results when I posted it)

jonas’: the only THE bug is THE timer bug!

okthen