XSF Discussion - 2018-02-05

Ge0rG: anything new regarding protoXEP?

hi marc! We got it in, as XEP-0401

marc: I've asked for feedback from the standards@ ML regarding the IBR extension, but got not much so far

marc: people would prefer a data form :(

Wow, cool. A data form instead of an ad-hoc command?

marc: a data form instead of a new IBR element.

marc: for the actual account registration, not for requesting the account

Okay, so that's what I used in the first place :D

Not a big problem IMO

I don't like it because it requires more complicated logic to figure out how to map fields to your client UI

Why? The field has a name and the names are defined in the XEP, no?

If you do it like in MAM with a basic set of predefined fields?

Zash: even then, I end up comparing a list of my own UI elements to a list of server-side form fields, with a need to fall back to a data form UI when a mismatch is found

Ge0rG, I don’t see the point; if you don’t want to support data forms, only support that specific setup of data forms and treat it as if IBR wasn’t supported at all/didn’t work otherwise.

also, Ge0rG: A host MUST NOT add new fields to the 'jabber:iq:register' namespace; instead, extensibility SHOULD be pursued via the Data Forms protocol as specified herein.

(from XEP-0077)

jonasw: you can override MUST NOT with another XEP

ugh

jonasw: the problem is to detect whether this is the "that specific setup of data forms"

FORM_TYPE would tell you

I don’t see a problem at all. compare form_type, compare set of var values, if they don’t match your expectations, fail ✏

jonasw: how will FORM_TYPE tell me? It will be just `jabber🇮🇶register`

that’s a start

rrr smileys. Ge0rG I assume you meant `jabber:iq:register`

pep.: yes, indeed. I need to fix that script finally

https://github.com/henry-luo/mark

no

Zash you're so focused on the past

no

search for namespace didn’t yield anything

doomed

Looked like HTML with {} instead of <>

Meh

Relevance to XMPP: Can't see any

yes that's exactly what we need, one new standard to replace all the existing ones https://xkcd.com/927/

It wont

obligatory

yaml adoption is limited, haha

didn't toml come to replace yaml?

I also enjoy how it has downsides to json like 'not as widely supported as json' but no downsides to xml

I guess it's as widely supported as XML ?

XML, the configuration file format from hell

Also, meh, I have Lua table notation. I don't need no JSON-XML hybrid

Good luck inventing a format for everything that doesn't suck at everything.

https://xmpp.org/extensions/xep-0239.html cover pretty much all the cases

Perfection