-
jonasw
hm, Link Mauve, I’m not sure I’m comfortable merging your change to xep-0050 without going through council
-
Link Mauve
It seemed very much editorial to me (https://github.com/xsf/xeps/pull/677/commits/b16e5025be007d9e4554beb127917f58246f980e for reference), but I can drop it from this PR and do another one for council.
-
jonasw
this removes one of two statements which contradict each other. technically, you could also have removed the requirement to ignore this attribute (and possibly replaced it with a requirement for it to b e "execute" or whatever), so I’m not sure.
-
Link Mauve
It didn’t make much sense to make a previously-ignored attribute required, only because it was marked as optional somewhere else.
-
Link Mauve
The other one is a MUST, this one is “optionally maybe add this”.✎ -
Link Mauve
The other one is a MUST ignore, this one is “optionally maybe add this”. ✏
-
lovetox
is there anything planned in caps2, that we have like a server caps hash?
-
lovetox
depending on the server, i have to send out min. 5 disco infos after a disco items
-
Link Mauve
lovetox, it’s already done, see §5.2.
-
lovetox
on each start of the client
-
Link Mauve
Uh?
-
lovetox
yes thats exactly what i would need
-
lovetox
yes Link Mauve need to discover httpupload, mucs, proxys, transports
-
Link Mauve
lovetox, if you mean that the server would keep a tree of all of its component’s ecaps2, the issue is that they could change at any moment, or even depend on who is asking.
-
lovetox
what the items of the domain could change depending on who is aksing?
-
lovetox
i mean yeah it could, but why should it
-
lovetox
a client could also announce different stuff depending on who is asking
-
Zash
was disco-sub a xep or how was it?
-
lovetox
we simply dont do ti
-
Link Mauve
lovetox, I’ve seen it done.
-
lovetox
yeah then this server should not use caps
-
lovetox
simple as that
-
Link Mauve
Why that?
-
Link Mauve
It’s still a valuable optimisation.
-
lovetox
i guess if he keeps a hash of its components *per* user
-
Link Mauve
Another issue is what to do when a component gets disconnected and reconnected?
-
lovetox
restart?
-
lovetox
nothing
-
lovetox
for longer time, then send out a updated hash
-
Zash
Bunneh: xep caps2
-
Bunneh
Zash: Sorry, I couldn't find a match
-
Link Mauve
xep ecaps2✎ -
lovetox
https://xmpp.org/extensions/xep-0390.html#usecases-stream-feature
-
lovetox
Zash
-
Link Mauve
Bunneh, xep ecaps2 ✏
-
Bunneh
Link Mauve: Entity Capabilities 2.0 (Standards Track, Experimental, 2017-06-14) See: https://xmpp.org/extensions/xep-0390.html
-
Zash
tanx
-
Ge0rG
What sucks about stanza counters in 0198 is that you can't say when the desync happened. I'm at 35k stanzas on my session, with ~20 stanzas too few counted by the server.✎ -
Ge0rG
What sucks about stanza counters in 0198 is that you can't say when the desync happened. I'm at 35k stanzas on my session, with ~20 stanzas too few counted by the client. ✏
-
Link Mauve
Ge0rG, don’t you get logging whenever that happens, on both sides?
-
Ge0rG
Link Mauve: no, i'm just receiving the last ~20 stanzas duplicated on resume
-
Link Mauve
Oh wow.
-
flow
Ge0rG, you know you are desync'd but still resume the desync'd stream?
-
daniel
Counting is surprisingly hard
-
daniel
I really wouldn't be surprised if i find a counting bug in Conversations
-
Ge0rG
flow: I know it, my client doesn't
-
Zash
IIRC especially when acting as client it gets awkward since you start twice from separate events
-
daniel
Yeah
-
daniel
I think part of the trickery is to make sure not to send stanzas into the stream before you are resumed. Or at least don't count them
-
daniel
But that goes for servers and clients