MozillaZine

Mozilla Privacy and Security Tutorial

Wednesday July 16th, 2003

Gunnar writes: "I have published a tutorial for Mozilla's privacy and security features. It explains and recommends settings. Feedback is very appreciated."


#20 cookies

by leafdigital

Thursday July 17th, 2003 3:54 AM

You are replying to this message

IMO the best answer for cookies is just to use the 'allow from originating web site only' option. This gives you almost all the security of the approach you've chosen (since let's face it, if it comes from the originating site you are generally going to click yes) and none of the hassle.

You said it might cause problems on smaller sites; does it really? I've had this option on ever since... well I don't know which version of Netscape introduced it but it was in Netscape 4 wasn't it? Ever since then anyhow. Which is quite a long time. And I've never encountered a Web site that had a problem with it, as far as I know.

Other comments:

* I recommend setting animated images to loop only once as it's a problem on the general Web, not just a few sites. However, your page explains the option which should be good enough to let anyone make their decision.

* In the bit about blocking banner ads you don't mention the 'Flash Click To View' extension which is AWESOME and erases all Flash ads while still letting you play Flash files whenever you want to (a game or whatever) with a very easy interface.

* About passwords: in reality nobody I've ever seen in RL can be arsed to turn on the encryption. :) I suppose you can still recommend it.

In general I think the article is excellent and is fairly easy to understand. You could work a little bit on dividing up sections clearly, or perhaps splitting the document into more pages, but other than that it's good.

There is one typographical problem, it's a fairly serious one:

* Do *not* (ever!) use underline to indicate headings or emphasis.

In printed media, using underline only demonstrates that you don't know what you're doing, it doesn't really cause a serious problem. (Note: There is such a thing as a horizontal rule, which is not the same as underline. You're using underline, not horizontal rules.)

On the Web, though, using underline is a much worse idea as it makes things look like links. Even though after a while you're going to realise it, it's still disturbing.

So that underline really should go. For example, on the final page:

[[

_The recommended settings for "Enable Javascript for" are:_

Check ...

]]

This can easily be changed. Simply use a subhead and reword the text as appropriate:

[[

* Recommended "Enable Javascript for" settings

Check...

]]

That's it really, nice document otherwise.

--sam