> On Nov 24, 2014, at 4:40 PM, Graham King wrote:
>
> Is a message without to/from permitted, or possible?
Certainly some stanzas can have both or one of to/from absent. XEP 297 can be
used to forward any stanza, and in a wide range of contexts. The requirements
apply to all forwarding case
Is a message without to/from permitted, or possible? I think the rules
here http://xmpp.org/rfcs/rfc6120.html#stanzas-attributes would prevent it:
To: "A stanza with a specific intended recipient (e.g., a conversation
partner, a remote service, the server itself, even another resource
associated w
While XEP 297 states the following requirement:
The original sender and receiver should be identified.
It is not clear how this requirement is fulfilled when one wants to forward the
stanza:
Hello
how is the sender and receiver to be identified (when known to the forwarding
entity)? Ad
So I have been thinking about this… where a user wants to forward a
conversation consisting of multiple stanzas, that it's probably not wise to
send them all in one stanza (even though XEP 297 doesn't explicitly preclude
this). I'm thinking XEP 297 should minimally contain a sentence: "Each st
On 24 November 2014 at 16:08, Cramer, E.R. (Eelco)
wrote:
> In the IoT mailing list (cc)?!
>
>
Ah! A mailing list I'd entirely missed for some reason.
Dave.
In the IoT mailing list (cc)?!
Cheers,
Eelco
On 24 Nov 2014, at 16:49, Dave Cridland
mailto:d...@cridland.net>> wrote:
On 24 November 2014 at 15:29, XMPP Extensions Editor
mailto:edi...@xmpp.org>> wrote:
Version 0.3 of XEP-0347 (Internet of Things - Discovery) has been released.
Abstract: Thi
On 24 November 2014 at 15:29, XMPP Extensions Editor
wrote:
> Version 0.3 of XEP-0347 (Internet of Things - Discovery) has been released.
>
> Abstract: This specification describes an architecture based on the XMPP
> protocol whereby Things can be installed and safely discovered by their
> owners
Version 0.3 of XEP-0347 (Internet of Things - Discovery) has been released.
Abstract: This specification describes an architecture based on the XMPP
protocol whereby Things can be installed and safely discovered by their owners
and connected into networks of Things.
Changelog: [See revision his
On 24 Nov 2014, at 15:13, Peter Waher wrote:
> Concerning spam: Is it only the editor’s list that is affected? How is spam
> kept away from the standards and iot lists?
>
Other lists only allow member posting.
/K
On 11/24/14, 8:13 AM, Peter Waher wrote:
Thanks Ash & Peter. I’ve resent the mail now.
Concerning spam: Is it only the editor’s list that is affected? How is
spam kept away from the standards and iot lists?
Only subscribers can send messages to those lists. We can't do that for
the editor lis
Thanks Ash & Peter. I’ve resent the mail now.
Concerning spam: Is it only the editor’s list that is affected? How is spam
kept away from the standards and iot lists?
Best regards,
Peter Waher
From: Ashley Ward [mailto:ashley.w...@surevine.com]
Sent: den 21 november 2014 13:10
To: XMPP Standard
* Philipp Hancke [2014-11-23 16:24]:
> Am 23.11.2014 um 15:16 schrieb Holger Weiß:
> >Why does XEP-0280 restrict its scope to message stanzas of type "chat"?
> >Wouldn't you usually expect to also receive copies of "normal" messages,
> >at least?
>
> See http://mail.jabber.org/pipermail/standards
12 matches
Mail list logo
