-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 15 February 2004 03:09 am, John Andersen wrote:
It can fool users into thinking they are being taken to FOO when in fact the link leads to BAR. (You gotta read closely). At BAR, all manor of evil code might be lurking.
-- _____________________________________ John Andersen
Yup, that is exactly the kind of shinanigan I want to preclude. None of this hidden file extension BS either. I don't even believe it should permit the user to launch an executable from the MUC. As far as images go, it's often the case that mailing lists don't like them, nor attachments. The mailing list could provide a profile in the headers which the client could suck in when the list is joined. When you compose messages to the list, you would be restricted by the rules of the list. The same might go for regular users who you have already received mail from. In that cased I would propose a manual override and let the rudeness be the responsibility of the user. I say this because some people who send you mail might be clueless as to what they are restricting. Obvious options would be available to the recipeant of such an override, e.g. a pop-up asking if you want to accept whatever feature they overrode. I'm mostly talking about text size, color, style, and perhaps font type. Also, I'm not really talking about HTML-ite. HTML screwed up the intended separation between semantic markup and style. I'm suggesting it be done right. That is, style would be in css, tagging would be in TML. There should be reasonable default styles available, and the ability to send your own style as part of the message document. STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAL0PmH2SF0i7rrGwRAqTbAJ9EcZyaPRpE8pKBXMLspfAogEK/wQCfVz1z fW+VI2QfKdNUGqHqUY4PKfw= =djPd -----END PGP SIGNATURE-----