[jdev] Re: Re: Gtalk implements jep-0136; any implementations for the rest of us?

[Jon Perlow]

Currently, there is no way currently to save conversations that are
encyrpted. The service can only handle the text bodies of message stanzas.
There is no way to manipulate the content of existing conversations. Is
there something specific you had in mind?

-Jon

On 2/9/06, Michal Vaner (Vorner) <michal.vaner at kdemail.net> wrote:
>
> Dne úterý 07 únor 2006 20:04 Jon Perlow napsal(a):
> > Hi,
> >
> > I am a developer on Google Talk and Gmail. We are working on a JEP
> proposal
> > and will send it out soon.
>
> Hello,
> I would like to know, will there be a way to save conversations that are
> encrypted, for example by gpg? Will there be a way to explicitly change
> the
> history?
>
> Thank you.
>
> > -Jon
> >
> > On 2/7/06, Peter Saint-Andre <stpeter at jabber.org> wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Remko Troncon wrote:
> > > >> Not sure at all; it just looks vaguely like 0136 since it's
> > > >> server-side, and it's possible for a client to disable the logging.
> > > >
> > > > Well, it's not JEP-136 :-) All the client can do is enable/disable
> it,
> > >
> > > but
> > >
> > > > the server does all the logging itself. This way, no matter what
> client
> > >
> > > you
> > >
> > > > use to connect, your conversations gets logged, and you don't need
> to
> > >
> > > send your
> > >
> > > > conversations over the wire twice either.
> > > >
> > > > I like this idea actually, because it falls under the 'keep the
> client
> > >
> > > simple'
> > >
> > > > principle. It's a lot easier than having to deal with concurrency,
> > >
> > > finding out
> > >
> > > > which conversations belong together, submitting them to the server.
> > > > It's
> > >
> > > safer
> > >
> > > > as well (what if your connection or your client dies, and you didn't
> > >
> > > have a
> > >
> > > > chance to commit your whole conversation), and it's incremental (a
> > >
> > > client needs
> > >
> > > > to keep track of the whole conversation before it can submit it)
> > >
> > > Yes, I chatted with one of the Google guys recently about this feature
> > > (which is why I asked about server-side JEP-0136 stuff a week or two
> > > ago). AFAIK this feature is something the client can enable or disable
> > > on a per-contact basis ("don't log this conversation, please"). Also I
> > > think this is something that would be supported (or not) by both
> servers
> > > if the parties are on separate domains, so if I say "disable logging"
> my
> > > server would ask the other server to do the same. But I'll let the
> > > Google guys describe it more, since I don't know all the details.
> > >
> > > Peter
> > >
> > > - --
> > > Peter Saint-Andre
> > > Jabber Software Foundation
> > > http://www.jabber.org/people/stpeter.shtml
> > >
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.1 (Darwin)
> > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> > >
> > > iD8DBQFD6M1RNF1RSzyt3NURAqHCAJ4x1hynKvLy+CJBWLieS2w4kiFjDACfW6jN
> > > jf1j8LsP6uF6KhuF7yQv/d4=
> > > =UVen
> > > -----END PGP SIGNATURE-----
>
> --
>
> Windows are like..
> windows. Shiny but fragile and expensive.
>
> Michal Vaner (Vorner)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20060209/9a0fe3a9/attachment-0002.htm>