The problem is that connections vary dramatically across different countries, and most people don't know what their upstream bandwidth is, which is the really critical question.
I don't think autodetecting it is viable; wherever we fetch a file from will complain, and it can be used to detect freenet installs... On Sat, Jul 08, 2006 at 01:03:17PM -0400, Colin Davis wrote: > IIRC, we aren't currently asking the user what their connection type > is, on installation. > > The better we can make freenet work by default on people's > computers, without overwhelming them, the more likely they are to > keep it running. I think we can best do that by enablign BW limiting > by default, to some percentage of their connection speed. > > I suggest that we ask the user what their connection speed is- Modem, > Cable (256K, 512, 1M, 2M), etc, and then try to auto-set a default BW > limiting. > > Additionally, we could tryy to be nice to their connection, by > autodetecting it. Have an option in the installer (and in the node) > to download a testfile from a fast source, such as Sourceforge.org, > and time the download- We can use this to determine the speed of the > connection, and set bandwidth limits accordingly. > > -Colin -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20060708/00e12c19/attachment.pgp>
