zinidjonas’, http upload (XEP-0363) has LC ended, but it's not reflected in the document
zinidjonas’, is it a known issue?
lnjhas left
goffihas joined
olihas joined
jonas’zinid, yes
jonas’kind ofg
zinidofg?
jonas’kind of
jonas’I had no weekend and am back at work, don’t have the energy to look into this now
zinidsure, just checking the condition of our xeps :D
goffihas left
goffihas joined
olihas joined
jonas’I think there is a vote on the LC result pending for council, but I’m not sure
lovetoxhas joined
labdsfhas joined
tahas joined
marc_has joined
lnjhas joined
frainzhas left
lorddavidiiihas left
frainzhas joined
lorddavidiiihas joined
Guusdwd ^ do you know?
moparisthebesthas joined
moparisthebesthas joined
zinidhas left
lumihas left
dwdHTTP upload... I can't recall the current status, but its last call brought up some security issues. I think those have been addressed, but I can't remember if we've done anything since.
rionhas left
j.rhas joined
Andrew Nenakhovhas left
Andrew Nenakhovhas joined
yvohas joined
j.rhas joined
yvohas left
Andrew Nenakhovhas left
Andrew Nenakhovhas joined
alacerhas joined
Marandahas joined
lumihas joined
olihas joined
Steve Killehas left
kokonoehas joined
Steve Killehas joined
edhelasI'd like to enforce Pubsub nodes to return their access model in their metadata, goffi what do you think ?
edhelasif not it's impossible for a client to know what to do/display when requesting a node
edhelasaccess_model and publish_model
edhelasit's a small change for 0060 but it will greatly help for the clients to display properly things in their UI
matihas left
alacerhas left
pep.PR against 0060, see what council says :)
alacerhas joined
edhelaswill do
KevWhile I'm happy for you to work that way if you want, it's a somewhat expensive way of saying "What do you think of the idea?".
Marandahas left
Ge0rGthe standard way for ""What do you think of the idea?" is to post to standards@ and not receive any responses, right?
ZashCorrect
edhelas:)
ZashNo responses, no objections!
Ge0rGZash: speaking of which. How's the GC1.0 removal going?
ZashGe0rG: From spec or code?
Ge0rGZash: from spec
ZashGe0rG: I did the same thing you did, realized that it was a larger task than initially expected and gave up half-way
Ge0rGZash: we should have bundled our efforts
j.rhas joined
Ge0rGOTOH, it is good to be independently confirmed in my conclusion
ZashWe could have given up twice as fast!
GuusI like how we're optimizing failure here!
SeveI prefer to discuss a bit before making a PR, so you know more or less if you are on the right path
Ge0rGRegarding GC1.0, there was a discussion on standards@, and some Council member proclaimed that they wouldn't oppose removing it if it doesn't make things worse.
pep.Seve: the issue is that you often don't get an answer :p
Ge0rGHowever, this is a very subjective matter. I've come to the conclusion that a MUC treating a presence update as a join and flooding me with message duplicates is worse than being dropped off properly.
SeveSad
Andrew Nenakhovhas left
olihas joined
igoosehas left
igoosehas joined
ZashSeve: Probably because most people don't bother replying with "Meh" or "Sounds fine but I don't really care about this that much"
flowGe0rG, Zash: If there where a git with the current state of your GC1 removal, people could and probably would collaborate and help (at least I would had a look too)
vanitasvitaehas left
Ge0rGflow: that's exactly the problem. We both started at the paragraph first mentioning GC1.0, tried to remove it and realized that it needs to be written from scratch.
moparisthebesthas joined
Ge0rGIf somebody had started removing the protocol pieces instead, things might move forward faster
flowI am not sure how that problem keeps you from creating a git where people could collaborate?
vanitasvitaehas joined
ThibGhas joined
flowI would even offer my repo, which would automatically create HTML diffs to the current xep45 version
flow(assuming the html diff tool is able to deal with xep45-sized xeps)
Ge0rGflow [10:50]:
> which would automatically create HTML diffs to the current xep45 version
Can we have that functionality please? Not as SaaS, but for use everywhere and anywhere?
ZashAh right, this problem
> Compliant multi-user chat services MUST accept [Groupchat 1.0]
Yagizahas left
Yagizahas left
Yagizahas joined
Ge0rGZash: prosody 0.11 is incompliant!
flowIIRC there was consensus that it's ok. And while I am a strong supporter of namespace bumps on incompatible changes, I'd also simply remove GC1 without an bump
GuusThat's a convenient tool! It'd be handy if it had a 'go to next change' action.
ThibGhas joined
lhas joined
Lancehas joined
Zashhas left
frainzhas left
Zashhas left
pep.oh wow that's cool
lumihas joined
karoshihas left
karoshihas joined
Sevevery nicey
pep.(Also scrolling down MUC takes some time..)
edhelasthat's nice yes, could be nice to navigate directly to the changes
Holgerhas left
Tobiashas left
vaulorhas joined
Zashhas left
Steve Killehas left
ThibGhas left
Yagizahas left
ThibGhas joined
Lancehas left
mrDoctorWhohas left
kokonoehas left
kokonoehas joined
matlaghas left
Lancehas joined
Holgerhas left
!xsf_Martinhas joined
Andrew Nenakhovhas left
vaulorhas joined
Andrew Nenakhovhas left
Holgerhas left
Holgerhas joined
matlaghas joined
Marandahas joined
Marandahas joined
olihas joined
kokonoehas joined
tuxhas joined
Lancehas left
lovetoxhas left
lskdjfhas joined
tuxhas joined
goffiedhelas: I think enforcing would need a namespace bump which is not really possible seing the current "draft" status of XEP-0060, but with a SHOULD instead of a MUST it would be a nice addition. Probably trying to do a PR and see what council say is a good way to move forward.
equilhas joined
moparisthebesthas left
Lancehas joined
Guushas left
rtq3has joined
alacerhas left
alacerhas joined
j.rhas joined
lorddavidiiihas left
andyhas left
ThibGhas left
ThibGhas joined
lorddavidiiihas joined
Marandahas joined
Marandahas joined
lorddavidiiihas left
jjrhhas left
jjrhhas joined
lorddavidiiihas joined
jjrhhas left
jjrhhas joined
lskdjfhas joined
neshtaxmpphas left
lovetoxhas joined
Ge0rGflow: that's awesome, at least on a 1920x1080 display :)
jjrhhas left
jjrhhas joined
kokonoehas joined
lskdjfhas joined
karoshihas left
karoshihas joined
Lancehas left
flownow even with colored xml diff for the brave: http://geekplace.eu/xeps/xep-muc-no-gc1/xml-colordiff.html
jonas’flow, http://geekplace.eu/xeps/xep-muc-no-gc1/diff-side-by-side.html can you make it so that it uses the full screen width?
jonas’it’s annoying to read even on a large display
flowjonas’, I can do whatever https://github.com/cygri/htmldiff can do
jonas’I don’t know what htmldiff can do
jonas’you probably know that better than I do, given that you’ve set it up
Lancehas joined
flowThe point is that I only use a python tool to generate the diff, and I don't know what the tool can do besides producing the output shown. From a quick look, the answer is probably "no"
ralphmhas joined
Half-ShotXhas joined
neshtaxmpphas joined
jmpmanhas joined
Lancehas left
lorddavidiiihas left
lorddavidiiihas joined
ThibGhas joined
j.rhas joined
Holgerhas left
j.rhas joined
Ge0rGThat color diff HTML shows as xml in my browser.
jonas’Ge0rG, because it’s a color diff of the XML
404.cityhas joined
404.cityhas left
Lancehas joined
Ge0rGI was lured by the .html file ending.
tahas joined
MattJYeah, don't view source on that :)
Ge0rGI just tapped the link 🤷
ThibGhas joined
ThibGhas joined
ralphmhas left
alacerhas left
tuxhas joined
tuxhas joined
tuxhas joined
flowthat is why I wrote "for the brave" :)
flowawaiting your GC1 removal PRs in case you want to collaborate on that
pep.I really wish I could see diffs of the changes, instead of reading the revision history in the XEP and wondering what happened
pep.In the end I'm reading the git version in the xeps repo anyway
Ge0rGpep.: yeah, a rendered diff version, even side-by-side, is a huge help for reviewing PRs
pep.Ge0rG, I meant in the XEPs themselves
Ge0rGpep.: we used to have that
pep.https://xmpp.org/extensions/xep-0045.html#appendix-revs this is useless to me
Ge0rGbefore The Big Crash
pep.I see
Ge0rGWe had a renderer that produced an inline-diff based on two revisions of a given XEP
Alexhas left
Ge0rGIt used to be like this: http://xmpp.org/extensions/diff/api/xep/0325/diff/0.2/vs/0.3
Ge0rGflow: how many hours of CPU time does htmldiff consume for 0045?
mimi89999has joined
Yagizahas left
Alexhas joined
Ge0rGAh!
> htmldiff build/xep-0045.master.html build/xep-0045.html > xep-0045.diff.html
> 393.65s user 0.12s system 99% cpu 6:33.83 total
moparisthebestfast, efficient
moparisthebestjust like you'd expect from python
ZashGe0rG: And you haven't borrowed Link Mauves toaster?
Ge0rGmodel name : Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz
Guushas left
zinidhardware is cheap nowadays I'm told, just upgrade
Ge0rGIt's running on a single core. You can't get cores an order of magnitude faster than that.
Ge0rGAnd even then it'd still be slow.
ziniddo you mean to say that I cannot just by more CPU? o_O That's strange :/
zinid*buy
zinidI'm also told that Python's GIL is not a problem at all
Kevhas left
zinidpython taliban is funny
moparisthebestjust wait for Link Mauve to rewrite it in Rust :D
ZashWLMRIIR is the new RIIR
moparisthebestit's better because then *we* don't have to do any work
sezuanhas left
Ge0rGBut it will be full of race conditions!
zinidjust lock everything
frainzhas left
ZashLaunch 200 instances of the process and accept bets on which will finish first
XSF Discussion - 2019-02-11