XSF Discussion - 2021-09-28

Zash, what are the chances that you'll make the '313 PR today? :)

Negative

ack

I've had some time to think about it and I'm not sure what I had in mind is enough, while at the same time complicates things more than I'd like.

Still not a fan of adding a boolean, that feels like a hack. And how would it work with MUC?

wasn't that the list-multi field of message types for mam?

or am I confusing things?

Zash, wanna spill your thoughts to the list? :)

Kev suggested a boolean. I suggested a list-multi, but that a) complicates things and b) neither seems to have nice discovery properies

I would like to, only my email client is modal and I'm trying to write something IETF related.

I think Dave's proposal, which I submitted an update to the XEP for, is the minimum engineering that avoids the problem we're currently seeing and that was causing GeOrG to veto advancement for. Something more engineered is possible, but won't necessarily be giving us any more value for the effort.

Kev: depending on how you define value, I suppose. If it is only about getting me away from "-1", then you are probably right

Did i fix it?

did you?

what did you not-fix?

Zash: you did.

An error when deploying a change to https://logs.xmpp.org/ resulted in an unclean state.

jonas’: you could add "duplicate fields in disco#info" to ojn checks

Ge0rG, what how why

jonas’: see the backlog in the Canal That Shall Not Be Named

Module reload somehow failed in the middle and it ended up with two of the things that add the `muc#roominfo_logs` field to disco#info

oh :)

jonas’: and it made yaxim fail to join with a timeout because the background thread crashed on the "invalid" disco

yep, read scrollback

any iTeam docker wizards here? :) I could use some feedback for https://github.com/xsf/xmpp.org/pull/981