XSF Discussion - 2023-01-09

> It was designed and marketed as the last framework one would need for developing apps for Windows. Well now it is officially deprecated and will not receive any new features any more. Classic

I don’t want to take away emus’ job but I'd personally be interested in an up to date list of people who are planning on going to the summit and a list of things people may want to talk about. https://wiki.xmpp.org/web/Conferences/Summit_25

I went to add Push 2.0, and as I hit save there was an conflict with your entry for the same topic, so I added my name :)

I think after I finish auth stuff, revisiting push (actually implementing something new) will be next on my list, so it's a good time to talk about it

I'm intending to go, but knowing there's a block booking coming for the hotel I'm holding off until I hear about that.

> Daniel: > 2023-01-09 12:18 (GMT+01:00) > I don’t want to take away emus’ job but I'd personally be interested in an up to date list of people who are planning on going to the summit and a list of things people may want to talk about. https://wiki.xmpp.org/web/Conferences/Summit_25 Hey, my bad, I will shoot a mail tonight

Although we're getting to the point that it might end up being too late.

MattJ Are you intending risking UK trains, or are you doing something else this year?

I'm risking the trains...

Quite a gamble, so I don't know what I'll do if I lose

Train AND plane!

Take the full week, squat the hackerspace with your sleeping bag :P

This way you can arrive at any point before summit!

why do both caps and caps2 include the hash as part of the node when requesting disco?

for caching, I think?

the answering client shouldn’t need to know that?

caching of what?

kinda like a HTTP ETag?

could allow returning a consistent reply when adding and removing features as well

there's a race condition; you broadcast hash(features) someone receives that and requests disco#info node=hash(features) ... you add some feature (+notify for example) so now caps is hash(features+x) ... you receive a request for hash(features), if you respond with features+x then the requester will get a response inconsistent with what they requested and conclude that you don't know how to do caps

Daniel, makes sense?

like, if you get a request where the node doesn't match your current feature set, you can ... do something

yes I guess...

All booked for Summit & FOSDEM 🛌️ 🚅️

> I think after I finish auth stuff, revisiting push (actually implementing something new) will be next on my list, so it's a good time to talk about it MattJ: the sasl upgrade tasks are still missing in prosody, right?

Would be nice to have an implementation to test monal against...

thilo.molitor: yes

MattJ: but planned?