On Sat, Jun 09, 2018 at 12:52:42AM +, Tedd Sterr wrote:
> 4) Proposed XMPP Extension: Ephemeral Messages -
> https://xmpp.org/extensions/inbox/ephemeral-messages.html
> Kev isn't entirely sure he even understands this one.
> Daniel has implemented burner messages before and doesn't think this
On Sun, May 13, 2018 at 12:38:03PM +0200, Jonas Wielicki wrote:
> On Samstag, 12. Mai 2018 19:55:52 CEST Paul Schaub wrote:
> > Hi!
> >
> > I get what you want to achieve, but I think it would be easier to define
> > disappearing messages for general XMPP (not only OMEMO).
> >
> > As already
On Sun, May 13, 2018 at 01:05:54PM +0200, W. Martin Borgert wrote:
> On 2018-05-13 12:38, Jonas Wielicki wrote:
> > On Samstag, 12. Mai 2018 19:55:52 CEST Paul Schaub wrote:
> > >
> > >
> > > This is an ephemeral message
> > >
> > >
> >
> > This is awful. It will require the
On Sun, May 13, 2018 at 12:40:40PM +0200, Jonas Wielicki wrote:
> On Sonntag, 13. Mai 2018 00:07:32 CEST Alexander Krotov wrote:
> > For unencrypted timed messages we need to require hinting the server
> > not to store the message, by the way.
>
> You do realize that th
On Sat, May 12, 2018 at 07:55:52PM +0200, Paul Schaub wrote:
> Hi!
>
> I get what you want to achieve, but I think it would be easier to define
> disappearing messages for general XMPP (not only OMEMO).
>
> As already stated, you cannot trust devices that announce support, to
> actually delete
On Sat, May 12, 2018 at 04:32:13PM +0200, Jonas Wielicki wrote:
> On Samstag, 12. Mai 2018 15:31:41 CEST Alexander Krotov wrote:
> > On Sat, May 12, 2018 at 10:45:49AM +0200, Florian Schmaus wrote:
> > > On 12.05.2018 10:14, Alexander Krotov wrote:
> > > > On Fri, Ma
On Sat, May 12, 2018 at 10:45:49AM +0200, Florian Schmaus wrote:
> On 12.05.2018 10:14, Alexander Krotov wrote:
> > On Fri, May 11, 2018 at 10:24:35AM +0200, W. Martin Borgert wrote:
> >> Quoting Alexander Krotov <ilab...@gmail.com>:
> >> Therefore it is orthogo
On Sat, May 12, 2018 at 01:36:45PM +0500, Ненахов Андрей wrote:
> сб, 12 мая 2018 г., 13:16 Alexander Krotov <ilab...@gmail.com>:
>
> > I want to be able to advertise to my contacts which of my devices
> > support timers, so devices that don't support them are not able to
On Fri, May 11, 2018 at 10:24:35AM +0200, W. Martin Borgert wrote:
> Quoting Alexander Krotov <ilab...@gmail.com>:
> > Disappearing messages without end-to-end encryption and forward
> > secrecy are useless at best. They give the user false sense of
> > security. That
On Thu, May 10, 2018 at 02:31:27PM +0200, VanitasVitae wrote:
> Am 10. Mai 2018 14:24:47 MESZ schrieb "Remko Tronçon" :
> >I don't see why a XEP for data retention hints needs to be tied to
> >other XEPs like
> >OMEMO, though.
>
> I'd also rather not tie it to OMEMO. The same
On Thu, May 10, 2018 at 02:24:47PM +0200, Remko Tronçon wrote:
> > In federated environment you can't control what client is used
> > by remote party, and if it really does delete messages after timer expires.
>
> True, but it would still be a useful in a situation where you trust
> the other
On Thu, May 10, 2018 at 09:02:18AM +0200, Philipp Hörist wrote:
> Your proposal seems very complicated and impossible to understand for
> normal Users
Users only need to understand the UI. As I imagine it, it will
consist of two actions: switching encryption to OMEMO+Timers (just
like you switch
I propose to extend OMEMO with disappearing messages.
There is already a thread with a subject: "Self-destruct" message timeout
deletion hints.
It started with this message:
https://mail.jabber.org/pipermail/standards/2016-October/031515.html
Continued in November:
13 matches
Mail list logo