Re: sending debian-private postings to gmail
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 25 May 2006 16:21:35 -0500
Ron Johnson <ron.l.johnson@cox.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ian Jackson wrote:
> > Kevin B. McCarty writes ("Re: sending debian-private postings to
> > gmail"):
> >> Ian Jackson wrote:
> >> [snip]
> >>> distributed to computers whose owners and operators cannot be
> >>> expected to refrain from processing the content in other ways.
> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>
> >> [...] If you are sufficiently paranoid, [...]
> [snip]
> >
> > However, it is _not_ silly to observe that Google are counting up
> > how many times certain keywords appear and providing reports to
> > their advertisers. We don't know exactly what those reports look
> > like but it might be quite easy to find out what topics are being
> > discussed on debian-private.
> >
> > It's clear that Google think they have the legal right (given to
> > them by the developer-user) to facilitate that and it's also clear
> > that they have no particular reason to spend effort thinking about
> > how to make it difficult for their advertiser customers to do that
> > kind of thing.
>
> ROT13? Such "encryption" would not hinder the NSA, but would bollox
> Google's keyword counting.
>
> Do any modern GUI MUAs do ROT13 anymore?
It's pretty trivial to write an 'action' for Sylpheed/Sylpheed-Claws to
do this for both encoding and decoding an e-mail.
UNAQ,
Wnpbo :-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEd1MFkpJ43hY3cTURAplnAJwOmRaSJdZkJyheGhK6XZ9E5wg8qQCfXAWa
7Mcwe3N4M3e+Z0mutwvNz58=
=hdCL
-----END PGP SIGNATURE-----
Reply to: