Hi,
My seednodes.ref is nearly 1mb in size, with (I worked out) 905 entries
in it. I've downloaded a couple from freenet, and they're both a lot
smaller, with about 50 entries. The one from Reskill has 49 entries. Is
the size of my seednodes.ref normal? I'm using build 5076.
Thanks,
Michal.
This bings me to mind why don't we compress the
http://freenetproject.org/snapshots/seednodes.ref with gzip or bzip2?
with regards,
Max Moritz Sievers
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Ok... seing that the seednodes.ref on the snapshot site is 2.5 mb, maybe
my 1 mb isn't that big.
___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at
Max Moritz Sievers wrote:
This bings me to mind why don't we compress the
http://freenetproject.org/snapshots/seednodes.ref with gzip or bzip2?
We do.
--
Mika Hirvonen [EMAIL PROTECTED]
http://nightwatch.mine.nu/
___
Support mailing list
[EMAIL
1MB doesn't sound unusual. 905 distinct nodes in 1MB's worth of space
does sound unusual. What's the date on your seednodes.ref? Maybe it's
using the classic routing scheme, with no estimators. Maybe you're
counting the entries incorrectly?
I just checked the 1.9MB seednodes.ref in snapshots,
$
S wrote:
1MB doesn't sound unusual. 905 distinct nodes in 1MB's worth of space
does sound unusual. What's the date on your seednodes.ref?
12th October 2003... that does seem a bit old.
Maybe it's
using the classic routing scheme, with no estimators.
Looking at
On Sunday 21 March 2004 13:28, Niklas Bergh wrote:
You mean like we do with
http://freenetproject.org/snapshots/seednodes.ref.bz2
That's nice to know but update.sh doesn't use it. So I guess most
Freenet-users download the big uncompressed file.
BTW: I'm on the list.
with regards,
Max Moritz
Max Moritz Sievers wrote:
On Sunday 21 March 2004 13:28, Niklas Bergh wrote:
You mean like we do with
http://freenetproject.org/snapshots/seednodes.ref.bz2
That's nice to know but update.sh doesn't use it. So I guess most
Freenet-users download the big uncompressed file.
Yes, it does.
2) Even after having the node up for a wile and(!)
successfully downloading content, the node more often
fails to route the request to other nodes than before
NG-routing. Wihtout NG routing I was able to have
request returned with 25 HTL with a data not found
error - a clear indication that