I've got a clean install of 561 that has been running for 20 hours. I set the announce delay to 3000 to speed things up, and have downloaded a bunch of stuff. I haven't done any deliberate key insertions, but I think my FEC download may have inserted missing blocks. I have 50 node references and the "client" side of Freenet seems to be up and working well.
My node has announcedTo Events=9, Value Change=20 (for the day). I have a lot of log entries like "Announcement failed to a292 2a5a a443 18ea 6666 b287 4f78 80bb 1642 050e at depth 2." And I have 49 incoming key requests. Question: What causes announcements to fail? In loadStats, I have 28 entries and globalRequestsPerHour: 3881.625 My concern is that when 0.5.1 launches there will be a LOT of nodes exactly like mine leeching from the network and bringing the big Freenet nodes to their knees. It's possible (and I'd say hard to tell) that the network just "doesn't need" my node at this point, or maybe it's deliberate that nodes are integrated this slowly. I'm using the node reference list the windows web installer defaults to. This seems like a key risk point for the release. If it's getting the same 50 nodes for every new user, those 50 are going to be hurting. Question: Is there anything that needs to be done to "spread the network out" during (or before) launch? -glenn _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
