Some things:
- other clients (chatbots) cannot discover capability to show buttons, nor
provide alternate text in case buttons are supported.
- how does this interact with XHTML-IM or its replacement(s)?
On Thu, Dec 6, 2018, 20:54 Dave Cridland wrote:
> Looks like a problem worth solving, but
Looks like a problem worth solving, but note below.
I'd prefer - non blockingly - the following:
* A click element. I feel that having an id and a click is superior given
the ambiguity of a text string.
* The examples should be changed to include a Big Red Button. I think the
worthwhile gag
XEP-0396 (Jingle Encrypted Transports - OMEMO) has been Deferred
because of inactivity.
Abstract:
Extension for JET introducing OMEMO End-to-End Encrypted Jingle
Transports.
URL: https://xmpp.org/extensions/xep-0396.html
If and when a new revision of this XEP is published, its status will
be
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Simple Buttons
Abstract:
This specification provides a way to send simple buttons.
URL: https://xmpp.org/extensions/inbox/buttons.html
The Council will decide in the next two weeks whether to accept this
proposal as an
XEP-0394 (Message Markup) has been Deferred because of inactivity.
Abstract:
This specification provides an alternative to XHTML-IM with rigid
separation of content and markup information, improving the resilience
against spoofing and injection attacks.
URL:
XEP-0395 (Atomically Compare-And-Publish PubSub Items) has been
Deferred because of inactivity.
Abstract:
This specification provides a mechanism to atomically Compare-And-
Publish items to a PubSub node.
URL: https://xmpp.org/extensions/xep-0395.html
If and when a new revision of this XEP is
XEP-0186 (Invisible Command) has been Deferred because of inactivity.
Abstract:
This document specifies an XMPP protocol extension for user
invisibility.
URL: https://xmpp.org/extensions/xep-0186.html
If and when a new revision of this XEP is published, its status will
be changed back to
I will make time to do a MIX spec edit next week
Steve
> -Original Message-
> From: Standards On Behalf Of Daniel Gultsch
> Sent: 06 December 2018 16:00
> To: XMPP Standards
> Subject: Re: [Standards] MIX (XEP-0369) channel discovery
>
> Hi,
>
> I ran into the same problem today and
Hi,
I ran into the same problem today and I support removing node=mix from
the disco#info.
Maybe with the filter aspect that Florian suggested. But querying a
JID should reveal whether or not that JID is a mix channel without
having to make two IQs.
As for disco#items that could potentially
