On May 5, 2008, at 5:49 PM, Matthew Toseland wrote: > [...] > - Freenet is slooooooooow, especially in this case where it had an > untweaked > browser. After a long delay, two sites loaded, after a longer delay, > several > sites loaded at once; this strongly suggests imho that the problem > is caused > by not finding the browser. User reports significant improvement in > speed > after a few minutes. > - Connection limit is definitely a problem: many images which should > be in the > same container not loading; same for the Potentially Dangerous Content > warning.
Surely the browser isn't the one which understands freenet containers. Are we coalescing requests for the same container internally? -- Robert Hailey
