On 18/12/14 02:39, Steve Dougherty wrote: > On 12/17/2014 03:02 PM, Arne Babenhauserheide wrote: >> Hi, >> >> I just had one of my new darknet contacts call me, saying “my Freenet >> site does not work anymore. It says the host localhost does not >> exist.” >> >> I was stupefied for a moment, until I realized that my darknet >> contact had just restarted the computer for the first time since >> installing Freenet. Then I was completely helpless: How do you start >> Freenet on Windows? It’s hard enough to explain on GNU/Linux (“go >> into a shell and ...”), but on Windows it’s a mystery to me. >> >> And for me that settles the debate about autostarting Freenet by >> default or not: Yes, the installation should by default make Freenet >> start automatically on startup. Anything else is a support >> nightmare. > The concern I had with this is that Freenet startup is fairly I/O heavy > and we don't want to significantly extend users' time between boot and a > responsive system. [0] IIRC the Freenet tray is accessible from the > start menu, and if people access Freenet through the tray it will start > if it is not already running. I assume your contact had bookmarks in > their browser? > > If we want to change the default despite these concerns I'm up for it. I > guess it's one fewer thing to be confused by. > > [0] https://bugs.freenetproject.org/view.php?id=6287 So what you are saying is the default is not NOT to start on startup?!
When was this massive, enormous change discussed? When the new installer was deployed? Was it imposed without discussion? All of the Freenet installers going back at least to 0.7.0 have always had start-on-startup. Xor has posted the obvious arguments as to why. I'm just pointing out that it's a major change which should have been discussed first, possibly here.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
