Ge0rGflow, Guus: could you reconfigure the ignite discourse to not auto-close threads after three months?
GuusGe0rG: would you mind asking for that in that discourse, for the relevant people to be involved?
GuusFwiw, I don't have a preference
Ge0rGGuus: does it have a "meta" tag?
Ge0rGI've only posted "smack" issues so far :
Ge0rG:>
evehas joined
Ge0rGGuus: thanks, posted as https://discourse.igniterealtime.org/t/please-disable-auto-closing-of-threads-after-3-months/85765
debaclehas joined
Lancehas joined
LNJhas joined
LNJCould someone regenerate the website, https://xmpp.org/extensions/ is outdated.
lnjhas left
lnjhas joined
Ge0rGLNJ: it _should_ get auto-generated, with ~2 hours of delay, so probably something broke.
Nekithas left
kokonoehas left
kokonoehas joined
Nekithas joined
eevvoorhas joined
eevvoorhas left
goffihas left
eevvoorhas joined
Nekithas left
Lancehas left
zachhas left
zachhas joined
delehas joined
delehas left
jubalhhas joined
jubalhwho 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
jubalhyep thats my goal
jubalhhowever if writing to the team also does the same. maybe I'll prefer this :)
jubalhthansk pep. I see the wiki link in the topic of that channel
marc_has joined
pep.They usually redirect you to the wiki because they can't remember everything people wanted to put in (which is fair enough) :)
Lancehas joined
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
GuusI just did.
Guusxsf/xeps was last built 19 hours ago
Guusseemed to have been successful
GuusI just kicked off a new build manually.
jonas’Guus, maybe a race condition then
jonas’thanks
Ge0rGah!
GuusThere's a webhook on that dockerhub build that I don't recognize: https://api.hub.sotecware.net
Guusah, Google reveals a likely culprit 🙂
Guusthe webhook has been failing for months though.
ralphmhas left
ralphmhas joined
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)
Guussure, no problem.
Guusmy browser gives a security warning on that URL btw
Guuscert 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 ;)
GuusI'll not bother bothering then 🙂
Ge0rGit used to be sotecware, but now it's abandonware
ralphmhas left
ralphmhas joined
sonnyhas joined
jonas’:P
Guus> someone with power (Guus maybe?) needs to kick the docker build job
@jonas` FWIW, I think you have the power too.
zachhas left
zachhas joined
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 :)
Guushey, Converse is having trouble doing the mention.
Guusah, k.
eevvoorhas left
Lancehas left
edhelasin https://xmpp.org/extensions/xep-0060.html#entity-discoveritems, where is the definition of the "jid" attributes of items
Link Mauveedhelas, in XEP-0030, disco#items.
edhelasfair enough
zachhas left
zachhas joined
Lancehas joined
waqashas joined
ralphmhas left
ralphmhas joined
adityaborikarhas left
adityaborikarhas joined
kokonoehas left
kokonoehas joined
Lancehas left
stpeterhas joined
Chobbeshas joined
adityaborikarhas left
adityaborikarhas joined
Chobbeshas left
Chobbeshas joined
Chobbeshas left
Chobbeshas joined
Lancehas joined
stpeterhas left
deepakhas left
deepakhas joined
moparisthebesthas joined
pdurbinhas left
Chobbeshas left
Chobbeshas joined
jubalhhas left
stpeterhas joined
evehas left
Dele (Mobile)has joined
evehas joined
jubalhhas joined
Chobbeshas left
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?
Ge0rGAdd sub elements to the feature element!
moparisthebesthas left
deepakhas left
moparisthebesthas joined
stpeterhas left
pep.Is there such cases currently where it can be confusing?
jubalhhas left
adityaborikarhas left
adityaborikarhas joined
zachhas left
Chobbeshas joined
waqashas left
Lancehas left
matlaghas left
matlaghas joined
Mikaelahas left
typikolhas joined
KevAdvertising RSM on its own doesn't really make any sense.
typikolhas left
KevRSM-for-Disco does, or RSM-for-MAM (which is really ust MAM, as MAM requires it).
Holgerhas left
KevRSM-for-Disco does, or RSM-for-MAM (which is really ust MAM, as MAM requires it).
KevRSM-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
Ge0rGRSM for president!
Holgerhas joined
sonnyhas left
pep.There could also be order-by, 413 :)
stpeterhas joined
flowShould 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?
peterhas joined
Lancehas joined
Mikaelahas joined
pep.So you'd include rsm when requesting, and then?
flowif 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)
flowright 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
flowbrrrr
pep.I need to have guarantees that the result is ordered
Ge0rGWe are speaking of disco#items only, right?
pep.Ge0rG: yeah
flowI 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
Ge0rGI'm actually looking for disco+search
flowGe0rG, 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
Ge0rGflow: but how are you going to split a single #info?
pep.What does the disco#items look like on conference.jabber.org?
flowGe0rG, cut in half? But yes, the issue is more pressing for disco#items
flowthat is why I would start with that and get some implementations experience
peterhas left
pep.Ge0rG: order-by might be something you want? You add a new condition "number of participants" for example :p
flowNote that mongoose's muc light uses RSM with disco#item: https://mongooseim.readthedocs.io/en/latest/open-extensions/muc_light/
flowbut I am not sure if the way they describe it is the way I would do it
Ge0rGpep.: 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?
Ge0rGAnd the result wasn't really worth it
pep.It would be too far-fetched to add that to disco#items
Ge0rGYeah, 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
Chobbeshas left
pep.I wouldn't create yet another xep
Ge0rGpep.: 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
Ge0rGThat was the easy step. The hard one is: deploy to jabber.org
MattJDon't underestimate the power of a moving glacier!
ZashEven the earth itself can't handle the pressure!
Link MauveLet’s just wait for it to be done melting, I’ve heard heat waves are going strong lately.
stpeterhas left
Ge0rGLink 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
Ge0rGpep.: global warming?
pep.Of course
Ge0rGpep.: 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 :)
Ge0rGIt's not very elegant, and I'm not sure how far it's supported by anyone, but it's the most logical syntax
Link MauveIt’s also not allowed by the schema, and will fail parsing in most parsers.
pep.I find it elegant enough :/
pep.Err
flowhmm I don't like child elements in <feature/>
flowpartly due the reasons Link Mauve mentioned
pep.What alternative is there?
pep.Declare new NSs for these combinations?
Link Mauvepep., for instance, a feature var='disco#info-with-order-by'.
pep.Right :/
Link MauveIt’s not a namespace, it’s a feature.
pep.Yeah ok
patrickhas joined
Mikaelahas left
waqashas joined
jubalhhas joined
Mikaelahas joined
Ge0rGAdd a comma separated list into the var, because why would you use xml syntax for it?
Chobbeshas joined
edhelasJSON
Ge0rGedhelas: thanks, I forgot.
Ge0rGBut then we rather should use DER.
LNJhas left
LNJhas joined
Dele (Mobile)has left
Dele (Mobile)has joined
debaclehas left
jubalhhas left
remkohas joined
Lancehas left
stpeterhas joined
peterhas joined
jonas’no that’d make zinid happy
ZashCBOR is the future!
remkohas left
Tobiashas left
Tobiashas joined
kokonoehas left
kokonoehas joined
edhelasjonas’ because you know how to make zinid happy ? 🤔
XSF Discussion - 2019-07-31