Supposedly, this now looks good if you drag/drop the address as a tile in your favorite brand of touchscreen device.
Guus
(but I didn't check for that)
Zash
I get 404 on https://xmpp.org/favicon-16x16.png and https://xmpp.org/favicon-32x32.png
Zash
but https://xmpp.org/favicon.ico seems to exist
Guus
ah, those are likely missing redirects
Guus
we keep those in https://xmpp.org/icons/favicon-16x16.png etc
Guus
(unsure why)
Guus
that's odd. It appears to be a pelican-based redirect?
Guus
Simply fixing the template to have the correct paths seems more sensible to me.
efrithas left
Guus
https://github.com/xsf/xmpp.org/pull/371 should fix it
Guus
anyone want to have a quick look?
Guus
hmmm, I might've jumped the gun there
intosihas joined
jonasw
I don’t think that’ll work with pelican
jonasw
you need to declare static directories
jonasw
and declaring content as static won’t work/blow up everything
jonasw
now all we need to do is to find out why the XEP list is incomplete
danielhas left
danielhas joined
Guus
jonasw: Yeah, i found that myself. I've revoked that PR, and created (and merged) another
Guus
I'll need to leave in 25 minutes, with many things to do until then.
Guus
I'm afraid you're on your own for the XEP list for today
jonasw
I see
jonasw
meh, I was hoping it would magically work
jonasw
that XEP list still frightens me
Guus
I can imagine
jonasw
I do not understand how that is run in docker at all. the docker build never invokes buildCompleteWebsite.sh
Alexhas joined
Guus
jonasw: I'm finding that the extensions root points to a temp dir
Guus
where the initial crash recovery took place
Guus
want me to remove that real quick?
jonasw
dooont
jonasw
I bet that file isn’t built
jonasw
that’d explain what I’m (not) seeing in the xmpp.org repository
jonasw
the built script is not invoked at all, if you remove that we won’t have any list✎
jonasw
the build script is not invoked at all, if you remove that we won’t have any list ✏
jonasw
(now at least it makes sense that I don’t find the invocation of the build script, thanks for taking a look)
jonasw
I’ll then figure out a cheap way to generate the XEP table with the docker things
Guus
ok. it's line 83-85 in the xmpp.org nginx config file on eos. Any iteamer should be able to help you
jonasw
thanks
Guus
I'll be offline during the weekend
jonasw
okay
jonasw
have fun
Guus
well, on mobile
Guus
tx
Martinhas left
Martinhas joined
waqashas joined
Guushas left
efrithas joined
Flowhas joined
pep.has joined
Guushas left
valohas joined
Guushas left
tim@boese-ban.dehas joined
vanitasvitaehas left
danielhas left
danielhas joined
danielhas left
tim@boese-ban.dehas joined
danielhas joined
Guushas left
Martinhas left
lumihas joined
Martinhas joined
Flow
Tobias: ping about https://github.com/xsf/xeps/pull/508#issuecomment-331070510
danielhas left
danielhas joined
tim@boese-ban.dehas joined
blablahas joined
emxphas left
intosihas left
Guushas left
Holgerhas left
danielhas left
danielhas joined
Valerianhas joined
danielhas left
danielhas joined
Wiktorhas joined
Holgerhas joined
iiro.laihohas joined
emxphas joined
intosihas joined
Guushas left
blablahas joined
stefandxmhas left
goffihas left
danielhas left
danielhas joined
Martinhas left
ralphmhas joined
Wiktorhas joined
intosihas left
intosihas left
intosihas joined
mimi89999has joined
intosihas left
intosihas joined
waqashas left
stefandxmhas joined
Valerianhas left
Guushas left
efrithas left
efrithas joined
jubalhhas left
efrithas left
danielhas left
jerehas joined
ralphmhas joined
zinidhas left
danielhas left
jjrhhas left
Yagizahas left
fp-testerhas joined
sonnyhas joined
jjrhhas left
fp-testerhas left
xnyhpshas joined
intosihas left
intosihas joined
jerehas joined
sonnyhas joined
iiro.laihohas left
Zashhas left
intosihas left
intosihas joined
ralphmhas left
intosihas left
intosihas joined
intosihas left
intosihas joined
lumihas joined
Zashhas left
jerehas joined
jubalhhas left
jubalhhas joined
jubalhhas left
Zashhas left
Flow
Ge0rG: How is "Battery saving (CSI) and push have different rules again" a problem?
Ge0rG
Flow: it's a matter of consistency
Ge0rG
Flow: also, nobody quite knows which rules to apply for push and csi
Flow
What would be better if they had consisten rules? Besides CSI deliberately specifies no strict rules at all (which is a good thing IMHO)
MattJ
Glad someone agrees with me :)
Flow
I mean it's not an easy thing to answer. It's one of the fields where experience from running code really matters
Flow
And something we eventually don't have to solve together with all the other more important and relevant issues you mention
dwd
Agreed. It's also not an easy thing to specify, and unclear what the interop failure by not doing so might be.
dwd
ie, it's a QoI issue. Some servers might be "better" (or at least more suitable for the client application), but everything should work one way or another eventually.
vanitasvitaehas left
Ge0rG
Flow: https://prosody.im/issues/issue/973 and check mod_csi_battery_saver source code for the many exceptions
Flow
Ge0rG: I fully aggree that it's important that we research working rules for CSI and Push. I just wanted to say that I don't think that those rules are necessarly the same, and that it's not an issue we should focus on right now
MattJ
Ge0rG, a couple of notes on that: it's still experimental code, and that report from you is good and healthy so we can improve the rules
Ge0rG
Flow: I never claimed I have the solutions
MattJ
The alternative would have been encoding all these rules into the XEP without prior experience
Valerianhas joined
Flow
Ge0rG: I would never insinuate you to have solutions ;)
MattJ
and once encoded, never being able to iterate on them and innovate
Flow
I do wonder if Session 2.0 and Bind2/SASL2 are two distinct steps into the right direction
Flow
(but maybe I should read the slides to the end)
Ge0rG
Flow: I'm pretty sure that CSI and push have the same underlying principles
Flow
Maybe, maybe not
Flow
Hrm, Message Routing 2.0 sounds a lot like XMPP 2.0
intosihas joined
Ge0rG
Flow: we decided to rename XMPP 2 into MR 2 to show it's not a complete reinvention of everything
Flow
Probably a good idea
Ge0rG
dwd: "everything should work one way or another eventually." is something I'd rather like to avoid, because then we'll end up with even more hairy corner cases.
Flow
Ge0rG: What happens in MR 2.0 with messages send to a full JID which is unavailable?
Flow
And is MR 2.0 also signled on s2s links?
Flow
*signaled
Ge0rG
Flow: MR2 should be also signalled on s2s, yeah. And messages are errored back
intosihas joined
Ge0rG
s2s MR2 will just follow the same semantics, and convert to MR1 clients
dwd
Ge0rG, CSI explicitly is not allowed to change the semantics of the stream, only introduce delay.
Ge0rG
dwd: I'm not sure what you are talking of
Flow
dwd: BTW I've published a new version of compare-and-publish and send a mail to standards@, not sure if you saw it yet. As always, your feedback is appreciated.
Valerianhas left
intosihas joined
Valerianhas joined
Ge0rG
MattJ: I'm okay with the rules being worded as MAY everywhere, as long as they are comprehensive according to current state of the art, and not the mess we have in 0280 now
jubalhhas joined
Flow
I don't think the CSI and Carbons situation is comparable
matlaghas left
Ge0rG
Flow: I'm talking about bad wording.
Guushas left
Ge0rG
Flow: and yeah, session2 and bind2 are distinct steps