On Monday 01 September 2008 19:45, Ian Clarke wrote: > On Wed, Aug 27, 2008 at 12:05 PM, Matthew Toseland > <toad at amphibian.dyndns.org> wrote: > > 1. Bootstrapping is working extremely slowly at the moment. It takes 5-10 > > minutes for a new node to get 10 peers according to the regular testing code. > > What, if anything, are we doing about this? What can we do about this?
We can solicit more seednodes. I've just done that. Beyond that I dunno, maybe it is worth investigating to see if there is a bug blocking things. I do think that improving Freenet's speed in general, even after bootstrapping, with things like FOAF and better handling of opennet node locations, will help us to gain and keep users. Nextgens will enable FOAF soon, this should help; when Vivee has some answers, hopefully we'll be able to sort out opennet swapping (we've talked extensively about simulations, hopefully this will be sorted soon). > > > 2. Many users get confused when we tell them that the ports may not have been > > forwarded, and this certainly leads to some uninstallations. We should fix > > the FNPPacketsSent-based not-port-forwarded detection, and only show that > > message if we have grounds to think we are not port forwarded. > > Ok, we should do it. Right. > > > 3. I suspect both this and the lack of content overlap with not knowing what > > to do with Freenet i.e. just the web interface isn't that interesting on its > > own, filesharing and chat need to be easy and obvious. > > Ok, so where do fixing these issues fit into our current priorities? As far as #3 goes, I'm open to suggestions. Searching: Lots of users want searching, and are disappointed when they don't get it. Integrating XMLLibrarian into freesites and into the homepage would help; making XMLSpider easier to use might help too; in any case, we need somebody to regularly insert an index. Chat: Saces is working on a plugin to implement FMS. This probably won't have a good web interface but may be a middle layer above WoT and below a web interface. A web interfaced embeddable chat plugin would be ideal, but making Frost use the WoT plugin would also be acceptable; we then have the question of how to make users aware of it if it's an external program. Filesharing: Again, how do we make users aware of Thaw, given it's an external program? Or do we tightly integrate the ThawIndexPlugin? I haven't used it, how useful is it? > IMHO they should be close to the top - without significant growth in > users we are screwed. Hopefully we can merge sdiz's branch soon. This should improve performance and reduce system impact, although to start with it should be off by default. My db4o branch is rapidly approaching usability; there is more work to do on inserts etc, but requests are working well, with fairly low resource usage. So that can be merged soon too. I've mentioned work related to speed above. And the port forwarding warning is a usability issue we need to deal with soon. > > Ian. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20080901/d50bc032/attachment.pgp>
