-
lovetox
can disco#items use rsm?
-
lovetox
is this its own XEP?
-
lovetox
if yes i dont find it
-
lovetox
ah its in 0059 described
-
flow
lovetox, its underspecified
-
lovetox
what part exactly flow?
-
Zash
Hmmmm, there's https://xmpp.org/extensions/xep-0059.html#examples
-
lovetox
Zash does prosody support that?
-
Zash
Nope
-
flow
lovetox, looks like I was wrong. I remebered the interaction with xep30 and xep59 to be underspecified, but that disco#items case (and the example) look straight forward
-
lovetox
question is how to discover that a server supports rsm on disco items
-
lovetox
because if i send a disco#items to conference.jabber.org with a rsm page size of say 50
-
lovetox
i get ddos with 18000 items
-
lovetox
because it does not support rsm ^
-
pep.
lovetox, I think edhelas is interested in disco + rsm
-
pep.
because apparently (pubsub) comment nodes are also huge
-
pep.
or something
-
flow
lovetox, do you need to discover support for disco#info+rsm?
-
jonas’
please don’t implement disco#items+rsm, I don’t want to (have to do it in the s.j.n code) :D
-
flow
it appears to me the idea behind xep59 § 3 is that you do it opportunistically
-
Zash
Wouldn't it be opt-in?
-
flow
Zash, how could it be not opt-in?
-
Zash
send <{disco#items}query><{rsm}set/></query>
-
Zash
as per the example
-
lovetox
flow yes see my example above
-
flow
right, I don't think you can do it any other way?
-
lovetox
otherwise you get DDoS
-
Zash
so if you don't, either you get everything or a truncated result if the server really doesn't want to send everything
-
flow
lovetox, but what is your plan b?
-
flow
first you need to know that the result set is very large
-
flow
which you may or may not a priori✎ -
flow
which you may or may not know a priori ✏
-
lovetox
plan b is not query disco#items
-
flow
so you tell your users, sorry can't list
-
lovetox
yes
-
lovetox
either server advertises it, or i dont display a list
-
lovetox
that was my idea
-
flow
I mean I think there no reason that we don't recommend services to announce that they support disco#info+rsm
-
flow
(of course we would have a discussion wether or note this announcement is recommended or required)✎ -
flow
(of course we would have a discussion whether or note this announcement is recommended or required) ✏
-
Zash
There's no specific feature or pattern for this already tho?
-
flow
Zash, pattern?
-
Zash
flow: eg writing "to announce support for disco+rsm, add <feature var=http:etc/disco#info+rsm}"
-
Zash
somewhere
-
flow
Zash, yes that is what I had in mind, and I don't think we have that (yet)
-
flow
hmm I have a private disco-rsm branch in my xeps/ repo
-
flow
and I am pretty sure this was discussed before
-
Zash
flow: or rather, "to announce foo + rsm support, concantenate the feature with "+rsm" and announce that"~
-
Zash
that'd be a pattern
-
flow
ahh yes, but at least for some foo+rsm you'd probably need to clarify in foo's xep how it would interact with rsm
-
pep.
fwiw I think this discussion also popped up when I added pubsub#rsm. And I don't know if I did remove the standalone rsm in disco (which doesn't make sense)
-
lovetox
it would really be nice if i could query my own servers MUC list in a good way
-
lovetox
i implement the interface to muclumbus but for mall company servers for example, it would be better to just disco#items
-
Zash
What if you had the muclumbus xmpp protocol to your local MUC?
-
pep.
Do we also need a similar system for say pubsub nodes, etc.
-
lovetox
Zash would be fine, though a bit too much for my taste
-
lovetox
hm Zash, no would be fine
-
lovetox
lets make a XEP out of it :)
-
Zash
Like https://xmpp.org/extensions/xep-0433.html
-
lovetox
i wonder why we not just used jabber search
-
lovetox
https://xmpp.org/extensions/xep-0055.html
-
lovetox
i see not much difference
-
lovetox
or non at all
-
lovetox
except some error are defined
-
lovetox
but yeah Zash would be a nice addition in prosody :)
-
Zash
Does anyone implement this dataform thing: https://xmpp.org/extensions/xep-0055.html#example-9
-
lovetox
yes gajim i think
-
lovetox
in the service discovery browser
-
Zash
<reported>?
-
lovetox
yes
-
lovetox
at least the last time i looked
-
pep.
lovetox, https://xmpp.org/extensions/xep-0433.html#design re jabber search
-
lovetox
i know only one server that has a user directory
-
Kev
zash
-
Kev
(Sorry, silly beta client, again) Zash: Yes, Swift and M-Link both do the data forms for that, unless I'm going mad.
-
Kev
(I can check in the morning for you if you want)
-
Zash
Kev: But including the <reported> stuff? I don't think I've ever seen that in action. Prosody doesn't support that part.
-
Kev
Oh. Uhm.
-
lovetox
Zash, without the reported its invalid
-
lovetox
the fields are encapsulated by <item>
-
Kev
Looks like Swift understands reported, at a glance.
-
lovetox
and you only have this in reported data forms
-
lovetox
thats not jabber search syntax
-
lovetox
thats XEP0004
-
Kev
Yep, M-Link also sends reported for xep55 as far as I can see (without doing much research).
-
eta
Kev: what beta client is this?
-
Kev
A heavy rework of Swift we're experimenting with.
-
eta
ah, nice