Re: Re: How much value does llvm provide for a low-use laptop?

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--hMRDAS53umgLBhPQ6GKO1gT5aWHdOifed
Content-Type: multipart/mixed; boundary="sFxhjWBx4s0s7CaSl4hugFaGhmBHB40R6";
 protected-headers="v1"
From: Allan Wegan <[email protected]>
To: [email protected]
Message-ID: <[email protected]>
Subject: Re: [gentoo-amd64] Re: How much value does llvm provide for a low-use
 laptop?
References: <CAK2H+eez8zQjL2FxcR7k4wNjKVMRhq8L_=4s5P7Tn_289Um_Vg@mail.gmail.com>
 <[email protected]>
 <[email protected]>
 <[email protected]>
In-Reply-To: <[email protected]>

--sFxhjWBx4s0s7CaSl4hugFaGhmBHB40R6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

>>> Please turn off the HTML posts.
>> His post is a multipart message containing an additional plaintext
>> version. If you saw the HTML version, your client is broken or
>> misconfigured.

> My client presented both versions as plain text, as arguably it
> should (because some broken clients don't send an appropriate plain
> text version if they're sending an HTML message).

The rare cases with no plaintext part can be handled by switching to the
source view. That cases are easily detected by the absence of any body
text in the plaintext view.

> But HTML when presented as such in mail or news is simply a
> vulnerability vector waiting to be exploited, and plenty of senders
> do just that with spyware (web bugs being the simplest) and malware.

Of course it is. Everything, that gets interpreted in any way, is
(including the whole email).

> So no responsible person will allow HTML mail to be processed and
> displayed as such on their machines, which in turn means no
> responsible person should choose to send it.

So you chosed to not process HTML in emails because of the security
implications. That is fine (even if it leaves me wondering how the web
looks like on your machine).

I dislike HTML in emails too (mostly because of common convoluted table
designs and ugly font/color choices). But others seem to like it and so
they use it. They either do not care or come to other conclusions
regarding the buggyness of current HTML/image parsers and the uglyness
of most HTML mails out there...
Fortunately one can chose whether to display that HTML or not - even if
some obviously have chosen to not use that freedom.

HTML mail is all about choice too.



--=20
Allan Wegan
<http://www.allanwegan.de/>
Jabber: [email protected]
 OTR-Fingerprint: E4DCAA40 4859428E B3912896 F2498604 8CAA126F
Jabber: [email protected]
 OTR-Fingerprint: A1AAA1B9 C067F988 4A424D33 98343469 29164587
ICQ: 209459114
 OTR-Fingerprint: 71DE5B5E 67D6D758 A93BF1CE 7DA06625 205AC6EC


--sFxhjWBx4s0s7CaSl4hugFaGhmBHB40R6--

--hMRDAS53umgLBhPQ6GKO1gT5aWHdOifed
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE+85rUTcaxx5VM7jOw7eVXIjLVC4FAlj1kQEACgkQw7eVXIjL
VC4kNg/+NZPLMJq9gJLtBUvaoJ55CB8VWREmmzBzY6s901OFdL+qorUue7ZQqAPC
c4qbvpqxrB6LtKnyjbdtGTWiINjDDLIFhh0mSC7EG+FE0zmR8KnYiIY+KLB4Xs02
LGASvhofwkdZCGWDGpqdY0yhUchzaj4u3oozYeOfIQZn5zlowlPBZO3O69X57Ky6
NbcjFB7aZqXQ+yRTuUeZCz52sQ7bjccIX5hZRadQ/oJIEkDyd1sv+j5UPoAqiUcu
wfwRq6S6jzxx1OOJv1CYQ9hLzvk0B3EsretmO6rKmEp/DcutvDOmEd+Ew59aDcOh
kwW7omvHNwgq9O9GyUW4EJT/X2BF+j1b0f5j80hyB56y2vEI8SHOrvqO2T+hafQf
CpAOwobArLlpr4Al5NbqsQoJcn66g8EwC+DIMHF7/pcV7bPJTXyAX/qHYf3Ejo6e
Soz0666my5mKrvfIJSQvbgxGEOuuA2AKek82Sz8nKBCN0DdweP6B4OiO2giEfz8q
TYcn5e+s0tTwkuaUyGSSV/WhrDq99eJT8u/4S+gjMZx9D43CVaUiaT5bTGVo5WO1
y0Lp+AXsTPxngokMV0/2lhJH80FVJc3WsEMdvtjR2PZODhog6b8O1bGFaaZfyHF3
/55ipHsxFyzmDNEhfvwkNMnc3aziiaUkzS265abwWEhaLpvkpyM=
=fLoc
-----END PGP SIGNATURE-----

--hMRDAS53umgLBhPQ6GKO1gT5aWHdOifed--