1. Re: off-server archives with MAM (Goffi)

2015-04-19 20:00 GMT+08:00, [email protected]
<[email protected]>:
> Send Standards mailing list submissions to
>       [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://mail.jabber.org/mailman/listinfo/standards
> or, via email, send a message with subject or body 'help' to
>       [email protected]
>
> You can reach the person managing the list at
>       [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Standards digest..."
>
>
> Today's Topics:
>
>    1. Re: off-server archives with MAM (Goffi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 18 Apr 2015 22:11:52 +0200
> From: Goffi <[email protected]>
> To: XMPP Standards <[email protected]>
> Subject: Re: [Standards] off-server archives with MAM
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 18/04/2015 11:03, Dave Cridland wrote:
>> Between XEP-0355 and carbons, I think you're covered already, at first
>> thought.
>
> Indeed the XEP-0355 has a mechanism to delegate MAM (or something else)
> to any entity under the control of the user. The issue here is that the
> data still go through the server.
>
> In France they have just voted a new law to allow "black box" to spy at
> the ISP/hosting level, so even if the archives are under user control,
> that doesn't prevent any data logging. I guess the old e2e encryption
> question need a solution really quickly.
>
> XEP-0355/Carbon + some e2e encryption XEP would allow to keep MAM and
> eveything under user control, at the price of some ping-pong with the data.
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Standards mailing list
> [email protected]
> http://mail.jabber.org/mailman/listinfo/standards
>
>
> ------------------------------
>
> End of Standards Digest, Vol 137, Issue 19
> ******************************************
>

Reply via email to