daniel> I think some HTTP libs don't allow you to specify header order
that crossed my mind too
Ge0rGI have a small nitpick about "These headers MUST be included in the HTTP PUT request" - it's not clear whether it relates to the headers that are in the XML or to the three allowed header names.
jonas’-1: The wording has a bug which can easily be misread as "the headers' order must be preserved", while the intent was to preserve the order of values of a given header, if multiple values are given ✏
jonas’Ge0rG, yep, that was another bit
jonas’I'll propose an updated wording in a minute
jonas’pep., I'll hijack your PR if I may
moparisthebestoh, well yea it would be best if header order wasn't required, especially if it wasn't intended
Ge0rGalso how do you sign a HTTP header?
moparisthebestpresumably you sign the header's value, but again, some wording
Ge0rGthere are schemes where signatures are sent out-of-band, and that wouldn't be compatible
jonas’proposed fix for the wording: https://github.com/xsf/xeps/pull/1140/commits/85ff424a9e2aab8a4aab56fcd490c341ae50b3a5
jonas’Ge0rG, there are standards for that, let's not go into that ;)
larmathanks jonas’ for the hotfix 🙂
jonas’Ge0rG, I'm sure HTTP header signing schemes are compatible with header reordering, as relative header order is AFAIK not guaranteed
Ge0rGjonas’: there be dragons
jonas’HTTP's dragons, not ours :)
moparisthebestok now I'm no-hesitation +1 :D
jonas’I'll be +1 with my patch
danielok. i'll restart voting *with* jonas' fix
jonas’Ge0rG, we already tighten down the available headers, which restricts what can be done anyway
larma+1
Ge0rGjonas’: I'm +1 with your patch
jonas’Ge0rG, tell that to daniel, I'm not chair anymore :)
Ge0rGjonas’: I'm pretty sure that most http libraries won't honor the order of equally named headers
daniel+1 here as well
Ge0rGdaniel: +1 ;)
danieli recorded your vote Ge0rG
moparisthebest+1 again
jonas’Ge0rG, let's not get into that here
danielok great. moving on
danielb) XEP-0030: remove security considerations preventing requests on a bare JID (https://github.com/xsf/xeps/pull/1145)
danieli'm on list for that
jonas’note that there's already a thread on list
jonas’but I, too, am on-list
jonas’haven't gotten around to read it yet
moparisthebestalso on-list, worries me a bit
jonas’(the thread has the subject [XEP-0030] we can't get basic information on a bare JID without presence subscription, it's also linked from the PR)
jonas’ack, -1 is my first inclination, too
Ge0rGon-list
jonas’but I'll read the rationale first, so please don't record that yet
larmaon-list
danielok thank you
daniel5) Pending votes
danielGe0rG and moparisthebest are pending on the four xeps proposed last week
Ge0rGYup.
danielnote the pubsub namespace one has technically already been vetoed
moparisthebestI'm +1 on all of them except Proposed XMPP Extension: PubSub Namespaces where I'm -1
jonas’I'm not sure what I voted on PubSub Namespaces, but the discussion has confirmed my perception that it should be -1 until fixed up as discussed on list
Ge0rGI'm still on-list
larmaI'm 0 on pubsub-ns, I feel there is need for clarification, but this is not how it should be
danieljonas’, i did record a -1 for you
jonas’excellent
jonas’speaking of, can I get a link to the current spreadsheet of doom? I lost it somehow :)
jonas’it's useful for editor work
moparisthebestfor logs sake I'm +1 on:
https://xmpp.org/extensions/inbox/compatibility-fallback.html
https://xmpp.org/extensions/inbox/call-invites.html
https://xmpp.org/extensions/inbox/replies.html
danielmoparisthebest, yes thank you i recorded that
moparisthebestalso I swear I voted -1 on https://github.com/xsf/xeps/pull/1126 but it was rejected already so meh :)
daniel6) Date of next
daniel+1w wfm
jonas’+1w wfm most likely
moparisthebestgood for me
larmawfm as well
Ge0rG+1W WFM, but I'll be on vacation the following two weeks
daniel7) AOB
jonas’covid19: "well, we'll see about that"
jonas’no AOB from me
moparisthebestno AOB
larmasame here
daniel8) Close
danielThank you everyone
larmaThanks daniel 🙂
jonas’Thanks daniel :)
moparisthebestthanks!
moparisthebestas an aside, the http header thing was fresh in my mind, because curl preserves both header order and case, and they recently added a backend using hyper (rust http lib) which preserves neither, which curl considered a bug :)
larmaWhat else would I use to craft special http requests than curl. I would consider this a bug as well if they lost those features...
jonas’larma, openssl s_client ;)
moparisthebestI just use curl for virtually everything http based
larmajonas’: that's already my XMPP client of choice :)
jonas’larma, see, it's a multi-protocol client ;)
pprrkshas left
pprrkshas joined
marc0shas left
marc0shas joined
Wojtekhas left
moparisthebestlarma, great job on all these XEPs by the way, seeing XEPs created with actual public code behind them is infinitely better than "in theory" XEPs
Wojtekhas joined
pep.“jonas’> pep., I'll hijack your PR if I may” < Sure.