marcOff-topic but will interest some of you: JMAP is a modern standard for email clients to connect to mail stores. It therefore primarily replaces IMAP + SMTP submission. It does not replace MTA-to-MTA SMTP transmission.
marcThe proposed standard is in "Last Call" : https://datatracker.ietf.org/doc/draft-ietf-jmap-core/
jonas’can we rm -rf it
ZashWe don't take kindly to JSON-HTTP APIs here
pep.Seems like "modern" is synonym for http/json really.
MattJOh no, my plans for modernxmpp have been revealed!
Ge0rGhttps://op-co.de/tmp/xform-buttons.html there, I rendered it for you
Link MauveHey, now that everything supports HSTS and HSTS preload, I could probably stop listening on port 80.
Link MauveZash, you should add HSTS preload to zash.se.
Ge0rGMitMs Link Mauve
Ge0rGZash: it's not scary enough.
Link MauveGe0rG, why would it be scary?
Ge0rGLink Mauve: XEP-0004 is scary..
Andrew Nenakhovhas joined
Link MauveIt’s not.
Ge0rGI mean, it's something that can be immediately discovered as scary, as opposed to MUC, which you need a decade to appreciate all the pitfalls of.
jonas’it is a weird mix of interactive forms, m2m protocol and overly generic search result reporting
Link MauveIt’s a bit under-specified, but it’s far from scary, even after ten years of working with it.
jonas’all while it is nearly unextensible in a way which doesn’t break existing implementations
Link Mauvejonas’, “search” result?
jonas’that reporting stuff
jonas’which re-uses some parts of the data form wire format in awkward ways
Ge0rGI tend to -0 Buttons because of:
- no i18n for the response, leading to surprising results for the user (you press "Ja" and it emits "yes")
- the obvious overlap with ad-hoc data command forms
jonas’Ge0rG, Ad-hoc data forms as in XEP-0050?
Link MauveZash, did you also have a version doing ad-hoc, btw?
ZashLink Mauve: no
Link Mauvejonas’, yeah.
ralphmWe were looking at something that fills roughly the same role as Facebook Message Templates: https://developers.facebook.com/docs/messenger-platform/send-messages/templates/
ralphmWhere besides buttons, you also have other UI elements that you can describe semantically, like image carousels.
ralphmXEP-0004 isn't _really_ the most ideal for this kind of use case.
Ge0rGButtons doen't have any of those except for buttons, and those are half-i18ned
ralphmWe haven't gone as far as defining an XML format for it yet, though.
MattJralphm, I'm currently working on similar (also mapping Facebook to XMPP), buttons will be a part of that
ralphmGe0rG: sure, just giving some context
Ge0rGralphm: I like the comparison to the facebook thing, BTW. I'm sure they invested heeavily into MVPing it
Ge0rGI'd love to see buttons and polls actually.
ralphmProblem with XEP-0004 is that all interactions are around, well, submitting a form.
ralphmThat's not the same as what Facebook-like templates do. There, you define an action for a specific button, taking some context into consideration.
ralphmBut yeah, polls is another such thing.
jonas’ralphm, though it’s possible to map the selection of a button from a set of buttons to list-single
ralphmjonas’: the problem is generally that you want a set of (hidden) fields to send along with such an action. So it might be that one button is like submitting a form, but the 'template' itself isn't one.
jonas’ralphm, you can have multiple forms
jonas’in a single message
jonas’(playing devil’s advocate here, I’m not convinced that XEP-0004 as-is is the right thing either)
ralphmjonas’: yes, sure, forms could be part of the presentation, but then you need some container format that is basically your (semantic) presentation of the whole thing.
ralphmI'm not convinced that the generic nature of XEP-0004 brings something to the table for this use case, but maybe it does.
Link MauveAll of this really sounds like 0050.
Link MauveWith extended 0004.
jonas’except that '50 can’t have message context
ralphmAnd maybe media sharing and maybe other things.
Ge0rGralphm: don't those things end up being the same if the action is defined by the original sender of the form?
ralphmGe0rG: well, maybe. The idea of XEP-0004 is that you can generically display any such form, without the client necessarily knowing about the business logic or meaning of fields.
Ge0rGralphm: so if we had 0004 with additional buttons and label i18n, we would have a superset of Buttons, Polls etc?
Ge0rGMaybe also with a specified way to convey this in regular messages?
ralphmI think that it is quite possible to do something similar to Facebook templates for XMPP, but not sure that using XEP-0004 of the basis of that format is the right approach. Clicking a button might trigger submitting a XEP-0004 form, similar to XEP-0050, sure.
pep.I agree that it does sound like 0050. Maybe there can be some work done to have it work with messages?
jonas’(recently I’ve been thinking that we should replace messages with IQs :-X)
Ge0rGjonas’: that idea was brought up before
pep.jonas’: what is the motivation?
jonas’pep., helps us get rid of all the reciepts and delivery uncertainty
ralphmI.e. you'd probably like at least buttons, lists (with media), and maybe a caroussel of the former.
ralphmanyway, there are two things here: the presentational format (semantic, not dictating formatting), and processing actions from them.
pep.jonas’: right I was also thinking about that when you mentioned IQs.
pep.You only get one level of acks though with this. People will still want "read" markers
ralphmfor more context, this is Facebook's view on buttons (that can be used in templates): https://developers.facebook.com/docs/messenger-platform/send-messages/buttons
Ge0rGpep.: yes, you IQ-send messages to your server and it does reliable delivery™
jonas’like with SMTP
jonas’on each step there is a defined handover; it’s not fire & forget
jonas’you have at-least-once semantics with SMTP, provided that required entities can be contacted within a timeout
jonas’(and don’t lie about taking responsibility for a message)