On Monday 10 December 2007 18:26, Tommy[D] wrote: > Matthew Toseland schrieb: > > On Sunday 09 December 2007 13:50, Jack O'Lantern wrote: > >> * Prefetching: loads links in a page in the background. If I understand > >> correctly, 0.7 already protects itself against this feature by > >> converting anchors to form submit buttons. This feature may be disabled > >> by setting "network.prefetch-next" to false. > > > > I believe this is off by default in most mozilla's/firefox's? It's harmless in > > 0.7 anyway, but it may cost some performance (due to tying up connections), > > or gain some (by prefetching high latency pages)... > > network.prefetch-next is default true for me.
Interesting. With the default max connections setting that could cost us more than it gains us.. there isn't any obvious way to fix it though.. > > >> * Safebrowsing: communicates the URL (and contents?) of each request to > >> a "safebrowsing provider" (Google is the default). This feature appears > >> to be deactivated in most, if not all, browsers by default. It may be > >> deactivated by setting "browser.safebrowsing.enabled" to false. > > > > Would be nice to detect it, I suppose we ought to mention it in the README...? > > What is its purpose? > > It is per default active, but uses per default a local list and no external provider for me. Its > goal is to check for fishing sites or other sites which try to harm you. The URL is checked against > a local list (or the providers list) and after that, the browser does give out a warning, if the > site is on the list. Hmmm I still don't understand - show an error message if the user types in a domain? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20071210/94208fb8/attachment.pgp>
