-
jonas’
I lack context
-
Link Mauve
jonas’, look up “420 blaze it”.
-
jonas’
do I want to at work?
-
Link Mauve
For science.
-
jonas’
I take that as a "heck no"
-
flow
420 implement it!
-
Ge0rG
flow, Guus: could you reconfigure the ignite discourse to not auto-close threads after three months?
-
Guus
Ge0rG: would you mind asking for that in that discourse, for the relevant people to be involved?
-
Guus
Fwiw, I don't have a preference
-
Ge0rG
Guus: does it have a "meta" tag?
-
Ge0rG
I've only posted "smack" issues so far :
-
Ge0rG
:>
-
Ge0rG
Guus: thanks, posted as https://discourse.igniterealtime.org/t/please-disable-auto-closing-of-threads-after-3-months/85765
-
LNJ
Could someone regenerate the website, https://xmpp.org/extensions/ is outdated.
-
Ge0rG
LNJ: it _should_ get auto-generated, with ~2 hours of delay, so probably something broke.
-
jubalh
who is writing the xmpp newsletter thingy? :)
-
pep.
commteam@muc.xmpp.org
-
pep.
There's also a wiki page you can edit if you want things to appear in the next one
-
jubalh
yep thats my goal
-
jubalh
however if writing to the team also does the same. maybe I'll prefer this :)
-
jubalh
thansk pep. I see the wiki link in the topic of that channel
-
pep.
They usually redirect you to the wiki because they can't remember everything people wanted to put in (which is fair enough) :)
-
jonas’
Ge0rG, the extension list is not coupled to the other generation process, it needs to be triggered manually
-
jonas’
someone with power (Guus maybe?) needs to kick the docker build job
-
Guus
I just did.
-
Guus
xsf/xeps was last built 19 hours ago
-
Guus
seemed to have been successful
-
Guus
I just kicked off a new build manually.
-
jonas’
Guus, maybe a race condition then
-
jonas’
thanks
-
Ge0rG
ah!
-
Guus
There's a webhook on that dockerhub build that I don't recognize: https://api.hub.sotecware.net
-
Guus
ah, Google reveals a likely culprit 🙂
-
Guus
the webhook has been failing for months though.
-
jonas’
Guus, that’s me
-
jonas’
the webhook is mine, and should be irrelevant
-
jonas’
I wanted to set something up which could do things when new XEPs are published
-
jonas’
but I didn’t get around to do it
-
jonas’
(sotecware.net is my domain)
-
Guus
sure, no problem.
-
Guus
my browser gives a security warning on that URL btw
-
Guus
cert probably outdated or not matching the domain or something.
-
jonas’
yeah
-
jonas’
I didn’t bother with maintaining that domain after I didn’t bother to write code for it ;)
-
Guus
I'll not bother bothering then 🙂
-
Ge0rG
it used to be sotecware, but now it's abandonware
-
jonas’
:P
-
Guus
> someone with power (Guus maybe?) needs to kick the docker build job @jonas` FWIW, I think you have the power too.✎ -
Guus
> someone with power (Guus maybe?) needs to kick the docker build job @jonas’ FWIW, I think you have the power too. ✏
-
jonas’
Guus, yes, but I don’t have my credentials on my work machine :)
-
Guus
hey, Converse is having trouble doing the mention.
-
Guus
ah, k.
-
edhelas
in https://xmpp.org/extensions/xep-0060.html#entity-discoveritems, where is the definition of the "jid" attributes of items
-
Link Mauve
edhelas, in XEP-0030, disco#items.
-
edhelas
fair enough
-
pep.
The day disco+rsm is a thing, or featureX+rsm is a thing, if in the disco#info I get I see MAM, featureX, rsm, how do I know what I can do? Do we need a different NS per combination?
-
Ge0rG
Add sub elements to the feature element!
-
pep.
Is there such cases currently where it can be confusing?
-
Kev
Advertising RSM on its own doesn't really make any sense.
-
Kev
RSM-for-Disco does, or RSM-for-MAM (which is really ust MAM, as MAM requires it).✎ -
Kev
RSM-for-Disco does, or RSM-for-MAM (which is really ust MAM, as MAM requires it).✎ ✏ -
Kev
RSM-for-Disco does, or RSM-for-MAM (which is really just MAM, as MAM requires it). ✏
-
pep.
I agree
-
pep.
Has this already been discussed somewhere? Something like Ge0rG said doesn't sound too bad :x
-
Ge0rG
RSM for president!
-
pep.
There could also be order-by, 413 :)
-
flow
Should a service even announce disco-with-rsm support? Wouldn't it be sufficient if the requesting entity would include i-can-do-disco-with-rsm flag into its disco request?
-
pep.
So you'd include rsm when requesting, and then?
-
flow
if the server supports it and the result set is large enough he will make use of it
-
flow
(that assumes we have defined, together with the i-understand-disco-responses-with-rsm flag, the semantic how that should exactly look like)
-
flow
right now the only reason I can come up with why a disco responser should announce that he supports rsm is to track how widespread the support is
-
pep.
OK, that's fine for rsm, now say order-by+disco is a thing
-
flow
brrrr
-
pep.
I need to have guarantees that the result is ordered
-
Ge0rG
We are speaking of disco#items only, right?
-
pep.
Ge0rG: yeah
-
flow
I don't want to go down that road right now. I would be happy if we had a solution to page through large disco result sets, like if you have a loooooot of pubsub nodes, using RSM
-
Ge0rG
I'm actually looking for disco+search
-
flow
Ge0rG, well there is nothing that prevents disco#info result from becoming too large for a single stanza (whatever "too large" is)
-
pep.
Lots of pubsub nodes is already a thing, edhelas says with comments the disco results easily becomes bloated✎ -
pep.
Lots of pubsub nodes is already a thing, edhelas says with comments disco results easily become bloated ✏
-
pep.
That's one reason why disco+rsm would be desirable
-
Ge0rG
flow: but how are you going to split a single #info?
-
pep.
What does the disco#items look like on conference.jabber.org?
-
flow
Ge0rG, cut in half? But yes, the issue is more pressing for disco#items
-
flow
that is why I would start with that and get some implementations experience
-
pep.
Ge0rG: order-by might be something you want? You add a new condition "number of participants" for example :p
-
flow
Note that mongoose's muc light uses RSM with disco#item: https://mongooseim.readthedocs.io/en/latest/open-extensions/muc_light/
-
flow
but I am not sure if the way they describe it is the way I would do it
-
Ge0rG
pep.: disco#items doesn't even contain that number, so you end up doing disco#info on each individual node. Last time I did it from yaxim, it took two hours.
-
pep.
Ge0rG: have you read order-by?
-
Ge0rG
And the result wasn't really worth it
-
pep.
It would be too far-fetched to add that to disco#items
-
Ge0rG
Yeah, jonas’ just needs to XEPize the MUC search protocol.
-
pep.
And then you could do what you're asking for, (and with rsm)
-
pep.
I think it's doable with the more or less generic bricks we have
-
pep.
I wouldn't create yet another xep
-
Ge0rG
pep.: I'm looking for a certain subset of all disco#info results embedded into the domain's disco#items
-
pep.
Sure
-
pep.
Create another condition for the order tag, by='number-of-participants' or sth, and let the server do the work, they already have all that info
-
Ge0rG
That was the easy step. The hard one is: deploy to jabber.org
-
MattJ
Don't underestimate the power of a moving glacier!
-
Zash
Even the earth itself can't handle the pressure!
-
Link Mauve
Let’s just wait for it to be done melting, I’ve heard heat waves are going strong lately.
-
Ge0rG
Link Mauve: this year, Greenland will melt enough ice for a 0.68mm sea level rise.
-
pep.
so.. <feature var="urn:xmpp:order-by:0"><feature var="http://jabber.org/protocol/disco#items" /></feature> this would do it?
-
pep.
(Or rsm instead of order-by)
-
pep.
Ge0rG: you haven't heard the news, that's a Chinese hoax
-
Ge0rG
pep.: global warming?
-
pep.
Of course
-
Ge0rG
pep.: you swapped the namespaces. order-by is an option of disco#items, not vice versa
-
pep.
OK sure, I don't care which way as long as we talk the same :)
-
Ge0rG
It's not very elegant, and I'm not sure how far it's supported by anyone, but it's the most logical syntax
-
Link Mauve
It’s also not allowed by the schema, and will fail parsing in most parsers.
-
pep.
I find it elegant enough :/
-
pep.
Err
-
flow
hmm I don't like child elements in <feature/>
-
flow
partly due the reasons Link Mauve mentioned
-
pep.
What alternative is there?
-
pep.
Declare new NSs for these combinations?
-
Link Mauve
pep., for instance, a feature var='disco#info-with-order-by'.
-
pep.
Right :/
-
Link Mauve
It’s not a namespace, it’s a feature.
-
pep.
Yeah ok
-
Ge0rG
Add a comma separated list into the var, because why would you use xml syntax for it?
-
edhelas
JSON
-
Ge0rG
edhelas: thanks, I forgot.
-
Ge0rG
But then we rather should use DER.
-
jonas’
no that’d make zinid happy
-
Zash
CBOR is the future!
-
edhelas
jonas’ because you know how to make zinid happy ? 🤔
-
jonas’
edhelas, he *does* like ASN.1
-
ralphm
hehe