Re: how to handle requests for HTML signatures

["Julian Y. Koh" <kohster () NORTHWESTERN EDU>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Styled text in email is bad, but livable as long as a text/plain version is
sent as well (the old arguments centered around storage and bandwidth
aren't as applicable these days, so as long as I have text/plain I'm
happy).  My biased and admittedly curmudgeonly viewpoint is that styled
text is a crutch for people who can't write and format text effectively.
:):)

Linked images I don't care too much about since most email clients can be
set to ignore those.

Attachments in general I've also accepted as a necessary evil.  Unless
they're word processing documents that contain just plain text.  Then see
"crutch" argument above.  :)

Embedded images are pure evil and can be a total pain to deal with
depending on the email client.

I'm starting to recognize top posting as a necessary evil given the
realities of reading email on mobile devices, but full quoting combined
with top posting is just lazy.  :):)

Having said all of that, if you don't help people with their signatures,
they'll just get someone else to do it, so you might as well take the
opportunity to get them to show _some_ measure of restraint, because that
someone else almost certainly won't.


-----BEGIN PGP SIGNATURE-----
Version: 9.9.1.287

wj8DBQFNAWIvDlQHnMkeAWMRAreXAJ9ae2aNQaN4G2ur8W3zXNq64IFQ4ACgtCK9
VF+GlLxw8sfN+WJ+KUawKC4=
=QZdI
-----END PGP SIGNATURE-----

-- 
Julian Y. Koh                         <mailto:kohster () northwestern edu>
Manager, Network Transport                         <phone:847-467-5780>
Telecommunications and Network Services         Northwestern University
PGP Public Key:<http://bt.ittns.northwestern.edu/julian/pgppubkey.html>