On 3 Feb 2015 11:58, Goffi go...@goffi.org wrote:
Having a node attribute is defined in 313 as specifying you want to
search a pubsub archive instead of another type of archive. I don't see
the confusion.
It's explained in XEP-0313, but I think it's a bad idea to use common
terminology to
On 03/02/2015 15:46, Dave Cridland wrote:
We can work around this in namespace delegation by adding an
attribute check in addition to namespace check, that would be better
than sending back the traffic to the server, even if it complicate the
XEP. I would still be more happy with an other
Hello everybody,
referring to commit:
https://github.com/winfried/XMPP-OTR/commit/76a5cf06a3728e042740c0e30ba535e55b2613a8
I know it's still work in progress, but I want to start from there to
say my two cents.
I think encrypting the whole stanza can be avoided in some cases.
Also, the only
On 2015-02-03 11:07, Winfried Tilanus wrote:
On 03-02-15 11:03, Ralph Meijer wrote:
Sure it will be short. However, some notes on limitations and security
considerations would also need to be added. If only to make it easier to
compare against other e2e proposals. If you want to make a start
Some clients do weird stuff like encoding XHTML-IM (which is probably
not a good idea at all). Also a XEP should give some advices on what to
allow, saying that history should be disabled by default, this kind of
things.
Also there is an OTR space-based discovery system which should be
Having a node attribute is defined in 313 as specifying you want to
search a pubsub archive instead of another type of archive. I don't see
the confusion.
It's explained in XEP-0313, but I think it's a bad idea to use common
terminology to associate MAM with an other XEP, without namespace.
Wiadomość napisana przez Daniele Ricci daniele.ath...@gmail.com w dniu 3
lut 2015, o godz. 12:20:
The only problem here is how to recognise the encrypted data? Is it a
text body or a stanza? Maybe we can use a type attribute to otr/,
revealing more metadata? Or maybe we could add a header
Of course, I was just talking about a deterministic way of describing the
encrypted data - and to save bandwidth.
Anyway the point of metadata leakage is valid. We (as in XMPP) do what we
can and we encrypt what we can. Anonymity was never the scope of XMPP.
Daniele
On 3 Feb 2015 12:59, Bartosz
Hi folks,
A decision will need to be made soon (by Board) whether we try out for GSoC
2015 as the XSF or not. It’d be helpful to know Very Soon if we have interested
mentors and projects available, so if folks are involved in running open-source
XMPP projects and are able to commit the time to
If you're interested in looking beyond the XMPP bowl there has been
very similar discussion in the post-XMPP messaging list:
https://moderncrypto.org/mail-archive/messaging/2015/001309.html
Multiple devices and key synchronization
On Tue, Feb 03, 2015 at 02:22:33PM +0100, Ralph Meijer wrote:
I think everyone in our community knows that XMPP, as currently
designed, has no simple mechanism to obscure who's communicating with
whom. Going into more detail, federation as in e-mail or XMPP has this
problem in both extremes:
I have created the membership application page for Q2 2015 at:
http://wiki.xmpp.org/web/Membership_Applications_Q2_2015
The following XSF members have to reapply:
* Yusuke Doi
* Wayne Franklin
* Artur Hefczyc
* Wojciech Kapcia
* Ben Langfeld
* Arc Riley
* Kevin Smith
* Paul Witty
* Andrzej
On 03.02.2015 10:04, Dave Cridland wrote:
On 2 Feb 2015 18:49, Peter Saint-Andre - yet pe...@andyet.net
mailto:pe...@andyet.net wrote:
On 2/2/15 5:22 AM, Hund, Johannes wrote:
Since it was undisclosed that even the NSA seems to have problems
breaking into OTR [1], it gained a lot of attention
On 3 Feb 2015 09:37, Florian Schmaus f...@geekplace.eu wrote:
On 03.02.2015 10:04, Dave Cridland wrote:
On 2 Feb 2015 18:49, Peter Saint-Andre - yet pe...@andyet.net
mailto:pe...@andyet.net wrote:
On 2/2/15 5:22 AM, Hund, Johannes wrote:
Since it was undisclosed that even the NSA seems
On 03/02/15 11:05, Goffi wrote:
G'day,
I have an issue that I mentioned in Brussel to Matthew with using MAM
(XEP-0313) for PubSub (XEP-0060)/PEP (XEP-0163).
Today to query a PubSub node with MAM, we need to do (according to
section 4):
iq to='pubsub.shakespeare.lit' type='set'
On February 3, 2015 10:37:14 AM WAT, Florian Schmaus f...@geekplace.eu wrote:
On 03.02.2015 10:04, Dave Cridland wrote:
On 2 Feb 2015 18:49, Peter Saint-Andre - yet pe...@andyet.net
mailto:pe...@andyet.net wrote:
On 2/2/15 5:22 AM, Hund, Johannes wrote:
Since it was undisclosed that even the
G'day,
I have an issue that I mentioned in Brussel to Matthew with using MAM
(XEP-0313) for PubSub (XEP-0060)/PEP (XEP-0163).
Today to query a PubSub node with MAM, we need to do (according to
section 4):
iq to='pubsub.shakespeare.lit' type='set' id='juliet1'
query xmlns='urn:xmpp:mam:0'
17 matches
Mail list logo
