On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland
[EMAIL PROTECTED] wrote:
Freenet 0.7 build 1178 is now available.
Wow! What a difference. 1178 is like a totally different program, with
respect to both cpu and memory usage. THANK YOU! It's no longer peaking
for minutes at a time. It's
On Friday 14 November 2008 23:21, Dennis Nezic wrote:
On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland
[EMAIL PROTECTED] wrote:
Freenet 0.7 build 1178 is now available.
Wow! What a difference. 1178 is like a totally different program, with
respect to both cpu and memory usage. THANK
Freenet 0.7 build 1175 is now available. Please upgrade. Changes:
- Handle the "Packet X sent Yms ago and still not acked" bug better. Don't
complain in the log until 10 minutes, then disconnect from the peer and log
the fact. We can then reconnect, but we will do so cleanly, so hopefully not
Freenet 0.7 build 1175 is now available. Please upgrade. Changes:
- Handle the Packet X sent Yms ago and still not acked bug better. Don't
complain in the log until 10 minutes, then disconnect from the peer and log
the fact. We can then reconnect, but we will do so cleanly, so hopefully not
get
Freenet 0.7 build 1174 is now available. This will be mandatory on Friday.
Changes are minimal, including an important bugfix in connection setup that
may help to solve the current packet not acked errors, support for longer
filenames in containers, a small bug in the logging code, adding
Freenet 0.7 build 1174 is now available. This will be mandatory on Friday.
Changes are minimal, including an important bugfix in connection setup that
may help to solve the current packet not acked errors, support for longer
filenames in containers, a small bug in the logging code, adding
Freenet 0.7 build 1173 is now available. This build is self-mandatory i.e. it
only talks to nodes running at least 1173. Freenet should be able to upgrade
itself automatically using "Update over Mandatory", pulling the data from
nodes that are "TOO NEW". If it doesn't, please upgrade manually
> On Sat, 8 Nov 2008 22:09:42 -0500,
> Dennis Nezic wrote:
>
> In this last 2min test of mine, all of the errors came from my 1173
> opennet peers. Only one of them was listed as "BACKED OFF" (I
> was/am connected to him for 4h49m)--the other two were (and still are)
> "CONNECTED" (for 48m and
> On Sun, 9 Nov 2008 00:22:11 +,
> Matthew Toseland wrote:
>
> Freenet 0.7 build 1173 is now available.
It is still using much more of (my 1.2GHz) cpu than I would like. It
regularly hovers at 100% for a few minutes, then calms down, then
repeats.
And, probably not unrelated, it is still
Freenet 0.7 build 1170 is now available, please upgrade! There are many
changes, built over the time since 1166 - the last 3 builds have been
critical bugfixes only. The most important changes:
- New compression formats: Files are compressed with gzip, bzip2 or lzma,
whichever gives best
> On Fri, 7 Nov 2008 17:02:55 +,
> Matthew Toseland wrote:
>
> Would you mind trying a recent testing build? update.sh testing /
> update.cmd testing ? The bugs in trunk have been largely fixed...
Yes--things seem to be running a lot better as of r23371--the jvm
hasn't hung yet after almost
On Fri, 7 Nov 2008 17:02:55 +,
Matthew Toseland [EMAIL PROTECTED] wrote:
Would you mind trying a recent testing build? update.sh testing /
update.cmd testing ? The bugs in trunk have been largely fixed...
Yes--things seem to be running a lot better as of r23371--the jvm
hasn't hung yet
Freenet 0.7 build 1170 is now available, please upgrade! There are many
changes, built over the time since 1166 - the last 3 builds have been
critical bugfixes only. The most important changes:
- New compression formats: Files are compressed with gzip, bzip2 or lzma,
whichever gives best
Freenet 0.7 build 1173 is now available. This build is self-mandatory i.e. it
only talks to nodes running at least 1173. Freenet should be able to upgrade
itself automatically using Update over Mandatory, pulling the data from
nodes that are TOO NEW. If it doesn't, please upgrade manually using
On Sat, 8 Nov 2008 22:09:42 -0500,
Dennis Nezic [EMAIL PROTECTED] wrote:
In this last 2min test of mine, all of the errors came from my 1173
opennet peers. Only one of them was listed as BACKED OFF (I
was/am connected to him for 4h49m)--the other two were (and still are)
CONNECTED (for 48m
On Sun, 9 Nov 2008 00:22:11 +,
Matthew Toseland [EMAIL PROTECTED] wrote:
Freenet 0.7 build 1173 is now available.
It is still using much more of (my 1.2GHz) cpu than I would like. It
regularly hovers at 100% for a few minutes, then calms down, then
repeats.
And, probably not unrelated,
Would you mind trying a recent testing build? update.sh testing / update.cmd
testing ? The bugs in trunk have been largely fixed...
On Friday 07 November 2008 03:18, Dennis Nezic wrote:
> Hrm.. sorry.. it seems to be working now that I'm using r23350.
>
> I was having all my problems with
Do you have any inserts queued?
On Friday 07 November 2008 02:28, Dennis Nezic wrote:
> > On Thu, 6 Nov 2008 15:13:11 -0500,
> > Dennis Nezic wrote:
> >
> > I should also add that my load averages (uptime) were at 80. I've
> > never seen them that high before.
>
> Update: I tried it again,
Do you have any inserts queued?
On Friday 07 November 2008 02:28, Dennis Nezic wrote:
On Thu, 6 Nov 2008 15:13:11 -0500,
Dennis Nezic [EMAIL PROTECTED] wrote:
I should also add that my load averages (uptime) were at 80. I've
never seen them that high before.
Update: I tried it
Would you mind trying a recent testing build? update.sh testing / update.cmd
testing ? The bugs in trunk have been largely fixed...
On Friday 07 November 2008 03:18, Dennis Nezic wrote:
Hrm.. sorry.. it seems to be working now that I'm using r23350.
I was having all my problems with
Hrm.. sorry.. it seems to be working now that I'm using r23350.
I was having all my problems with r23352--which I could have sworn was
referenced in freenet-stable-latest.jar.url this morning :|.
Anywho, sorry for the noise.
> On Thu, 6 Nov 2008 15:13:11 -0500,
> Dennis Nezic wrote:
>
> I should also add that my load averages (uptime) were at 80. I've
> never seen them that high before.
Update: I tried it again, except this time I accidentally forgot to
give it a seednodes.fref. The first attempt, the same thing
> On Thu, 6 Nov 2008 14:42:35 -0500,
> Dennis Nezic wrote:
>
> ., constantly using 100% cpu since being launched.
I should also add that my load averages (uptime) were at 80. I've never
seen them that high before.
> On Thu, 6 Nov 2008 14:02:40 +,
> Matthew Toseland wrote:
>
> Freenet 0.7 build 1169 is now available. Please update. No massive
> changes, but some important bugfixes which hopefully will fix some of
> the connectivity problems that have been reported recently:
I'm having a LOT of trouble
Please forward the below to FMS. Also, if update doesn't work, please run
update.sh / update.cmd manually. Thanks.
On Thursday 06 November 2008 14:02, Matthew Toseland wrote:
> Freenet 0.7 build 1169 is now available. Please update. No massive changes,
> but some important bugfixes which
Freenet 0.7 build 1169 is now available. Please update. No massive changes,
but some important bugfixes which hopefully will fix some of the connectivity
problems that have been reported recently:
- Fix announcing to the same node more than once, disconnecting, wasting lots
of announcements.
Freenet 0.7 build 1169 is now available. Please update. No massive changes,
but some important bugfixes which hopefully will fix some of the connectivity
problems that have been reported recently:
- Fix announcing to the same node more than once, disconnecting, wasting lots
of announcements.
Please forward the below to FMS. Also, if update doesn't work, please run
update.sh / update.cmd manually. Thanks.
On Thursday 06 November 2008 14:02, Matthew Toseland wrote:
Freenet 0.7 build 1169 is now available. Please update. No massive changes,
but some important bugfixes which
On Thu, 6 Nov 2008 14:02:40 +,
Matthew Toseland [EMAIL PROTECTED] wrote:
Freenet 0.7 build 1169 is now available. Please update. No massive
changes, but some important bugfixes which hopefully will fix some of
the connectivity problems that have been reported recently:
I'm having a LOT
On Thu, 6 Nov 2008 14:42:35 -0500,
Dennis Nezic [EMAIL PROTECTED] wrote:
., constantly using 100% cpu since being launched.
I should also add that my load averages (uptime) were at 80. I've never
seen them that high before.
___
Support mailing
On Thu, 6 Nov 2008 15:13:11 -0500,
Dennis Nezic [EMAIL PROTECTED] wrote:
I should also add that my load averages (uptime) were at 80. I've
never seen them that high before.
Update: I tried it again, except this time I accidentally forgot to
give it a seednodes.fref. The first attempt, the
On Thu, 6 Nov 2008 21:28:38 -0500,
Dennis Nezic [EMAIL PROTECTED] wrote:
.. BUT it was still consuming all the cpu!--supposedly not
doing anything!? At this point I turned the logger back on, and to my
horror, it immediately filled to over 70MB, 69.9 of which were errors
of the
Hrm.. sorry.. it seems to be working now that I'm using r23350.
I was having all my problems with r23352--which I could have sworn was
referenced in freenet-stable-latest.jar.url this morning :|.
Anywho, sorry for the noise.
___
Support mailing list
On Monday 27 October 2008 22.27.05 Matthew Toseland wrote:
> We have widespread reports
>
> PLEASE UPGRADE ASAP!
>
> If this is as bad as it looks we may have lost a _lot_ of users through it.
I just upgraded to 1166, and now everything looks much better on my system,
even fms/thunderbird has
We have widespread reports of serious problems with 1165: failure to bootstrap
on opennet, etc. This seems to be caused by the NullPointerException's in
PeerNode that was fixed weeks ago in trunk but never released. I should have
done a release at the time with only that change. Anyway, 1166 is
We have widespread reports of serious problems with 1165: failure to bootstrap
on opennet, etc. This seems to be caused by the NullPointerException's in
PeerNode that was fixed weeks ago in trunk but never released. I should have
done a release at the time with only that change. Anyway, 1166 is
On Monday 27 October 2008 22.27.05 Matthew Toseland wrote:
We have widespread reports
PLEASE UPGRADE ASAP!
If this is as bad as it looks we may have lost a _lot_ of users through it.
I just upgraded to 1166, and now everything looks much better on my system,
even fms/thunderbird has begun
Freenet 0.7 build 1165 is now available. Please let me know if the auto-update
doesn't fetch it, I will insert it soon (but feel free to update manually
first and report bugs!). Changes include:
- Hard bandwidth limiting for *all* packets, and fairer scheduling between
peers and between
Freenet 0.7 build 1165 is now available. Please let me know if the auto-update
doesn't fetch it, I will insert it soon (but feel free to update manually
first and report bugs!). Changes include:
- Hard bandwidth limiting for *all* packets, and fairer scheduling between
peers and between
Freenet 0.7 build 1164 is out. Please let me know if auto-update doesn't work.
The main change in 1164 is no-swap-on-opennet. This should greatly reduce
location churn on the majority of the network, and in simulations (thanks
vive, code will be committed shortly) improves performance in pretty
Freenet 0.7 build 1164 is out. Please let me know if auto-update doesn't work.
The main change in 1164 is no-swap-on-opennet. This should greatly reduce
location churn on the majority of the network, and in simulations (thanks
vive, code will be committed shortly) improves performance in pretty
On Tuesday 16 September 2008 00:20, Mr. Flibble wrote:
> Just had to update manually.
> This seems to happen now and again, where sometimes it will update
> automatically after I click on the "Update" request, other times it says
> it's downloaded it and will restart, and it just restarts with
Just had to update manually.
This seems to happen now and again, where sometimes it will update
automatically after I click on the "Update" request, other times it says
it's downloaded it and will restart, and it just restarts with the same
old version.
Maybe this is due to it not downloading
On Tuesday 16 September 2008 00:20, Mr. Flibble wrote:
Just had to update manually.
This seems to happen now and again, where sometimes it will update
automatically after I click on the Update request, other times it says
it's downloaded it and will restart, and it just restarts with the
Freenet 0.7 build 1163 is now available. Please upgrade, it will be mandatory
in a week. Mostly this is internal code cleanups (and a few internal
bugfixes), but there are a few user visible changes:
- Fixed the first-time wizard, which was having major problems (showing pages
with no CSS,
Freenet 0.7 build 1163 is now available. Please upgrade, it will be mandatory
in a week. Mostly this is internal code cleanups (and a few internal
bugfixes), but there are a few user visible changes:
- Fixed the first-time wizard, which was having major problems (showing pages
with no CSS,
Freenet 0.7 build 1159 is now available. Please upgrade, let us know if
auto-update doesn't fetch it for you. This build will be mandatory on Monday
the 8th of September. Major changes:
- Significant work on the temporary buckets code. This should fix the memory
problems that many experienced
Freenet 0.7 build 1159 is now available. Please upgrade, let us know if
auto-update doesn't fetch it for you. This build will be mandatory on Monday
the 8th of September. Major changes:
- Significant work on the temporary buckets code. This should fix the memory
problems that many experienced
Freenet 0.7 build 1160 is now available. Sorry for the two updates in one day,
but you'll like this one. As soon as 1160 is mandatory, on Friday, FOAF
routing will be automatically enabled (unless you turn it off in the
configuration). Friend-Of-A-Friend routing is a way of taking our peers'
Sorry for the late announcement. Freenet 1155 is available, mandatory on the
13th (Wednesday), let us know if the auto-update doesn't manage to find it.
Changelog:
- Opennet bootstrapping: improved support for low MTUs. The packets we use to
bootstrap a new opennet node, or to re-bootstrap a
Sorry for the late announcement. Freenet 1155 is available, mandatory on the
13th (Wednesday), let us know if the auto-update doesn't manage to find it.
Changelog:
- Opennet bootstrapping: improved support for low MTUs. The packets we use to
bootstrap a new opennet node, or to re-bootstrap a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salvatore Del Popolo a ?crit :
> Hello,
> I installed Freenet 0.7 on a Linux machine, Ubuntu distribution 7.10. I
> downloaded and unpacked the .tar.gz file and I ran the command:
> ./run.sh start
>
> It seems all ok, but when pointed my browser,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salvatore Del Popolo a écrit :
Hello,
I installed Freenet 0.7 on a Linux machine, Ubuntu distribution 7.10. I
downloaded and unpacked the .tar.gz file and I ran the command:
./run.sh start
It seems all ok, but when pointed my browser, lynx, to
Hello,
I installed Freenet 0.7 on a Linux machine, Ubuntu distribution 7.10. I
downloaded and unpacked the .tar.gz file and I ran the command:
./run.sh start
It seems all ok, but when pointed my browser, lynx, to
127.0.0.1:/wizard/, I received the message saying that the page is
not
Hello,
I installed Freenet 0.7 on a Linux machine, Ubuntu distribution 7.10. I
downloaded and unpacked the .tar.gz file and I ran the command:
./run.sh start
It seems all ok, but when pointed my browser, lynx, to
127.0.0.1:/wizard/, I received the message saying that the page is
not
Florent Daigni?re wrote:
> Freenet 0.7 build 1152 is now available; It has some new features but
> is mostly about bugfixes. It will be mandatory on the 15th.
>
> If you are still using a 1.4 JVM it is time to consider upgrading; it
> might be the last 1.4-compatible build we produce.
>
> On a
Freenet 0.7 build 1152 is now available; It has some new features but
is mostly about bugfixes. It will be mandatory on the 15th.
If you are still using a 1.4 JVM it is time to consider upgrading; it
might be the last 1.4-compatible build we produce.
On a side note, the manual updating scripts
Florent Daignière wrote:
Freenet 0.7 build 1152 is now available; It has some new features but
is mostly about bugfixes. It will be mandatory on the 15th.
If you are still using a 1.4 JVM it is time to consider upgrading; it
might be the last 1.4-compatible build we produce.
On a side
Freenet 0.7 build 1152 is now available; It has some new features but
is mostly about bugfixes. It will be mandatory on the 15th.
If you are still using a 1.4 JVM it is time to consider upgrading; it
might be the last 1.4-compatible build we produce.
On a side note, the manual updating scripts
Freenet 0.7 build 1151 is now available. Please let me know if auto-update
doesn't work. This build includes various minor bugfixes, and some more work
on the datastore. A couple of branches are seeing major work, on a new
datastore implementation, and on moving the client layer queue into a
Freenet 0.7 build 1151 is now available. Please let me know if auto-update
doesn't work. This build includes various minor bugfixes, and some more work
on the datastore. A couple of branches are seeing major work, on a new
datastore implementation, and on moving the client layer queue into a
Freenet 0.7 build 1150 changelog (sorry for the delay!):
- Chinese translations for a lot of the UI.
- Add The Freenet Applications Freesite to the default bookmarks.
- Some CPU usage optimisations.
- Fix a seednodes bug ("seeding for" count was bogus).
- Fix an infinite loop in shrinking
Freenet 0.7 build 1150 changelog (sorry for the delay!):
- Chinese translations for a lot of the UI.
- Add The Freenet Applications Freesite to the default bookmarks.
- Some CPU usage optimisations.
- Fix a seednodes bug (seeding for count was bogus).
- Fix an infinite loop in shrinking
Freenet 0.7 build 1145 is now available. Please upgrade (your node should
download the new build automatically, if it doesn't tell me). Hopefully this
will be the last build before 0.7.0, or at least the last one with major
changes. Please test it thoroughly and report any bugs you find.
Freenet 0.7 build 1143 was released yesterday, and is mandatory tomorrow.
Sorry for the lack of changelogs. Here they are for the last few builds:
1141:
- Don't give up so easily when loading plugins. We were having some problems
with plugins failing to load.
1142:
- Show one-line summaries of
Freenet 0.7 build 1143 was released yesterday, and is mandatory tomorrow.
Sorry for the lack of changelogs. Here they are for the last few builds:
1141:
- Don't give up so easily when loading plugins. We were having some problems
with plugins failing to load.
1142:
- Show one-line summaries of
Freenet 0.7 build 1139 is now available, please upgrade, it will be mandatory
on Wednesday. The only change in 1139 (other changes require further testing
and will be released in 1140 soon), is that we now ignore nodes with less
than 40% uptime when deciding whether we are the closest node for
Freenet 0.7 build 1139 is now available, please upgrade, it will be mandatory
on Wednesday. The only change in 1139 (other changes require further testing
and will be released in 1140 soon), is that we now ignore nodes with less
than 40% uptime when deciding whether we are the closest node for
Freenet 0.7 build 1138 is now available. Please upgrade, it will be mandatory
on Sunday. Major changes:
- Stop trying to contact seednodes after announcement has succeeded.
- Make the opennet warning dismissable, but it will come back after a restart.
- Some stats fixes that hopefully will help
Freenet 0.7 build 1136 is now available. Please upgrade. I forgot to announce
1135; a big part of 1136 is fixing bugs in 1135. Apologies for the recent
node crashes...
Changes:
1135:
- Increase the redundancy on splitfiles from 150% to 200%. Your node only
needs to download 100% of this to
Freenet 0.7 build 1132 is now available, and will be mandatory on Saturday.
Please upgrade ASAP. The main change in this build is a large number of
bugfixes to the client layer, which hopefully have fixed the stalling
downloads bug. Please tell us if you still get downloads progressing quickly
Freenet 0.7 build 1131 is now available, please upgrade. Major changes:
- Stop sending the old-format (very large) SSK messages. Other minor changes
aimed at avoiding sending huge packets (which frequently cause connectivity
problems, excessive resends etc).
- Improvements to the stats that
Freenet 0.7 build 1131 is now available, please upgrade. Major changes:
- Stop sending the old-format (very large) SSK messages. Other minor changes
aimed at avoiding sending huge packets (which frequently cause connectivity
problems, excessive resends etc).
- Improvements to the stats that
Freenet 0.7 build 1130 is now available. Please upgrade. This build fixes
various bugs mostly in the client layer, hopefully including the bug that was
causing downloads to stall, and including a bug causing bogus collisions on
SSKs, which may have harmed Freemail and ARKs. 1130 is mandatory on
Freenet 0.7 build 1129 is now available and will be mandatory on Sunday.
Please upgrade. Changes include an important stats bug which was causing
major problems for some nodes, and a few minor bugs. Also, we have been
working on the installer: it now creates a firefox profile customised for
Freenet 0.7 build 1129 is now available and will be mandatory on Sunday.
Please upgrade. Changes include an important stats bug which was causing
major problems for some nodes, and a few minor bugs. Also, we have been
working on the installer: it now creates a firefox profile customised for
Freenet 0.7 build 1127 is now available. It will be mandatory on Thursday.
Please upgrade ASAP. This build includes a wide range of bugfixes and one or
two new features:
- Transport layer fixes related to losing key trackers, resulting in hanging
packet throttle - we were no longer able to send
Freenet 0.7 build 1127 is now available. It will be mandatory on Thursday.
Please upgrade ASAP. This build includes a wide range of bugfixes and one or
two new features:
- Transport layer fixes related to losing key trackers, resulting in hanging
packet throttle - we were no longer able to send
Freenet 0.7 build 1126 is now available (sorry). Please upgrade, it will be
mandatory on Saturday. This contains a series of bugfixes for the last two
builds, relating to the new SSK messages, and the output bandwidth stats
(which affect the number of requests the node accepts, so are
Freenet 0.7 build 1125 is available, please upgrade as it will be mandatory on
Saturday. There are a couple of major changes:
- Transfer backoff. Ordinary backoff was not dealing with transfer failures,
we now have a separate mechanism for backoff after a transfer failure.
- Split up some SSK
Freenet 0.7 build 1125 is available, please upgrade as it will be mandatory on
Saturday. There are a couple of major changes:
- Transfer backoff. Ordinary backoff was not dealing with transfer failures,
we now have a separate mechanism for backoff after a transfer failure.
- Split up some SSK
Freenet 0.7 build 1126 is now available (sorry). Please upgrade, it will be
mandatory on Saturday. This contains a series of bugfixes for the last two
builds, relating to the new SSK messages, and the output bandwidth stats
(which affect the number of requests the node accepts, so are
Freenet 0.7 build 1124 is now available. Please upgrade, it will be mandatory
on Friday. Changes include:
- Send queued blocks in the order they were queued, rather than in "random"
notify order. This should reduce the number of failing block transfers.
- Fix a few NullPointerException's,
Freenet 0.7 build 1124 is now available. Please upgrade, it will be mandatory
on Friday. Changes include:
- Send queued blocks in the order they were queued, rather than in random
notify order. This should reduce the number of failing block transfers.
- Fix a few NullPointerException's,
Freenet 0.7 build 1123 is now available. Please upgrade (hopefully your node
will do this for you). Major changes:
- Fix a bunch of problems with the link level / connection setup code, found
in simulations.
- Tune the database parameters to try to avoid long stalling waiting for
background
Freenet 0.7 build 1123 is now available. Please upgrade (hopefully your node
will do this for you). Major changes:
- Fix a bunch of problems with the link level / connection setup code, found
in simulations.
- Tune the database parameters to try to avoid long stalling waiting for
background
Freenet 0.7 build 1122 is now available, and will be mandatory on Wednesday.
Please upgrade. This build includes many improvements/bugfixes, including:
- Fix a bug that was causing a large number of BlockTransmitter's to get stuck
when a connection was lost.
- Reduce the max HTL to 10, after 10
Freenet 0.7 build 1122 is now available, and will be mandatory on Wednesday.
Please upgrade. This build includes many improvements/bugfixes, including:
- Fix a bug that was causing a large number of BlockTransmitter's to get stuck
when a connection was lost.
- Reduce the max HTL to 10, after 10
Freenet 0.7 build 1119 is available and will be mandatory on Monday. Please
upgrade. The last few builds were seriously broken in various ways. Sorry for
the recent mess... :| Some bug fixes, and some minor features, exposed (or
sometimes caused) larger bugs, and I didn't properly test
Apologies for the new mandatory just after the last build, but it's worth it.
Build 1116 has various improvements to connectivity for nodes with low MTUs
and/or evil firewalls. Such nodes cannot successfully send or receive large
UDP packets. Connecting to seednodes has always used such big
Freenet 0.7 build 1115 is now available, and will be mandatory on Monday.
Please upgrade. Changes:
- Link level congestion control should work better.
- More HTL changes: 10 hops at HTL 15, then 14 hops, then 4 hops at HTL 1. We
will reduce the max HTL to 10 in the next build and that'll be it.
Freenet 0.7 build 1115 is now available, and will be mandatory on Monday.
Please upgrade. Changes:
- Link level congestion control should work better.
- More HTL changes: 10 hops at HTL 15, then 14 hops, then 4 hops at HTL 1. We
will reduce the max HTL to 10 in the next build and that'll be it.
Freenet 0.7 build 1113 is now available (and will be mandatory tomorrow).
Changelog:
- Various fixes to how we handle HTL.
- Lots of client layer fixes (mostly relating to splitfile downloads and the
cooldown queue).
- Major bugfixes to per-node failure tables and ULPRs.
- Improvements to the
Freenet 0.7 build 1112 is now available. It will be mandatory on Thursday so
please update ASAP (if your node has auto-update enabled it will do this for
you). This build features a number of substantial changes (I apologise for
the length of this mail!):
- Major changes to HTL (the means by
Freenet 0.7 build 1112 is now available. It will be mandatory on Thursday so
please update ASAP (if your node has auto-update enabled it will do this for
you). This build features a number of substantial changes (I apologise for
the length of this mail!):
- Major changes to HTL (the means by
Freenet 0.7 build is now available. Please upgrade! This build will be
mandatory on Monday, and includes many improvements:
- Much faster swapping (via queueing swap requests for a short period rather
than rejecting them).
- Don't delete downloads.dat.gz (the file containing the persistent
Freenet 0.7 build is now available. Please upgrade! This build will be
mandatory on Monday, and includes many improvements:
- Much faster swapping (via queueing swap requests for a short period rather
than rejecting them).
- Don't delete downloads.dat.gz (the file containing the persistent
Freenet 0.7 build 1109 is now available. Please upgrade ASAP. This build will
be mandatory on Tuesday, and includes some critical bugfixes and major new
features:
- The "my node stops using bandwidth after N hours" bug is fixed.
- Ultra-Lightweight Passive Requests and Per-node Failure Tables
Freenet 0.7 build 1109 is now available. Please upgrade ASAP. This build will
be mandatory on Tuesday, and includes some critical bugfixes and major new
features:
- The my node stops using bandwidth after N hours bug is fixed.
- Ultra-Lightweight Passive Requests and Per-node Failure Tables are
Freenet 0.7 build 1108 is now available. Please upgrade, it is mandatory on
Tuesday. This build includes lots of changes, bugfixes and improvements:
- Some memory optimisations in the client layer code (the client layer is
responsible for most of Freenet's memory usage if you have
101 - 200 of 552 matches
Mail list logo
