On Tue, 8 Jan 2019 at 18:23, Florian Schmaus wrote:
> On 08.01.19 17:00, Jonas Schäfer wrote:
> > On Dienstag, 8. Januar 2019 16:50:43 CET Georg Lukas wrote:
> >> * Jonas Schäfer [2018-12-14 16:18]:
> >>> I think adding a distinct feature is a good idea. Even if clients don’t
> >>> act on it
On Tue, Jan 08, 2019 at 04:54:22PM -, Jonas Schäfer wrote:
> This message constitutes notice of a Last Call for comments on
> XEP-0410.
>
> Title: MUC Self-Ping (Schrödinger's Chat)
> Abstract:
> This protocol extension for XEP-0045 Multi User Chat allows clients to
> check whether they are
On 08.01.19 17:00, Jonas Schäfer wrote:
> On Dienstag, 8. Januar 2019 16:50:43 CET Georg Lukas wrote:
>> * Jonas Schäfer [2018-12-14 16:18]:
>>> I think adding a distinct feature is a good idea. Even if clients don’t
>>> act on it (I’m not sure what they could (not) do by knowing that the
>>>
Am Di., 8. Jan. 2019 um 16:55 Uhr schrieb Jonas Schäfer :
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
I’m not sure. Is the intent of the XEP to keep me reliably connected
to a MUC or is it intended to figure out if I’m connected
Yes, I think a distinct feature is needed, and that feature should indicate
support for the optimisation in §3.3.
On Fri, 14 Dec 2018 at 15:01, Georg Lukas wrote:
> Hello,
>
> I'd like to ask for a Last Call for XEP-0410. It's got implemented in
> two clients and two servers so far:
>
> -
On Tue, 8 Jan 2019 at 16:55, Jonas Schäfer wrote:
> This message constitutes notice of a Last Call for comments on
> XEP-0410.
>
> Title: MUC Self-Ping (Schrödinger's Chat)
> Abstract:
> This protocol extension for XEP-0045 Multi User Chat allows clients to
> check whether they are still joined
On Dienstag, 8. Januar 2019 17:54:22 CET Jonas Schäfer wrote:
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
Yes, sadly. The introduction covers this quite nicely.
> 2. Does the specification solve the problem stated in the
On Tue, 8 Jan 2019 at 16:54, Jonas Schäfer wrote:
> This message constitutes notice of a Last Call for comments on
> XEP-0280.
>
> Title: Message Carbons
> Abstract:
> In order to keep all IM clients for a user engaged in a conversation,
> outbound messages are carbon-copied to all interested
This message constitutes notice of a Last Call for comments on
XEP-0410.
Title: MUC Self-Ping (Schrödinger's Chat)
Abstract:
This protocol extension for XEP-0045 Multi User Chat allows clients to
check whether they are still joined to a chatroom.
URL: https://xmpp.org/extensions/xep-0410.html
This message constitutes notice of a Last Call for comments on
XEP-0363.
Title: HTTP File Upload
Abstract:
This specification defines a protocol to request permissions from
another entity to upload a file to a specific path on an HTTP server
and at the same time receive a URL from which that file
This message constitutes notice of a Last Call for comments on
XEP-0280.
Title: Message Carbons
Abstract:
In order to keep all IM clients for a user engaged in a conversation,
outbound messages are carbon-copied to all interested resources.
URL: https://xmpp.org/extensions/xep-0280.html
This
On Dienstag, 8. Januar 2019 16:50:43 CET Georg Lukas wrote:
> * Jonas Schäfer [2018-12-14 16:18]:
> > I think adding a distinct feature is a good idea. Even if clients don’t
> > act on it (I’m not sure what they could (not) do by knowing that the
> > server does (not) support it), it is useful to
* Jonas Schäfer [2018-12-14 16:18]:
> I think adding a distinct feature is a good idea. Even if clients don’t act
> on
> it (I’m not sure what they could (not) do by knowing that the server does
> (not) support it), it is useful to meter the deployment in the wild.
>
> I suggest to use
13 matches
Mail list logo
