Hi,
As most of you have probably noticed, the server has suffered
of downtimes recently ... It's a known issue: we have moved it
physically to a new chassis because of hardware problems.
I would have announced it if it was planned ^-^
Everything ought to
Hi,
Freenet-ext #11 is out... It fixes the jvm segfaulting problem
on native 64 bit systems...
Your node might not be able to auto-update because of that bug.
Please replace your freenet-ext.jar file from your freenet
folder for that one :
Freenet 0.7 build 999 is now available. Here is a sum up of the changelog :
* #900 Get rid of unnecessary pings in BlockTransmitter. => should
reduce the memory footprint (Zothar)
* Get rid of messages unclaimed for more than an hour (Zothar)
* Improvement on
Hi,
Build 974 has been released, it features :
* A bugfix on the N2NTM code : the flood shouldn't occur
anymore when your peers have updated.
* The /?key= security bug has been fixed
* The timeout handling has been restored as it was on
971
Hi,
Build 971 is now out ; It's likely that people running builds
older than 970 won't be able to add new references from newer
builds... The node might tell them that "The integrity of the
reference has been compromized!". You will have to update in
order
Hi,
For those who have experienced problems installing/updating
freenet last night, I apologize; One of our script has "cleaned
up" the directory, removing the freenet-stable-latest.sha1 file
from mirrors.
It has been sorted out and shouldn't occur again.
Hi,
Just to keep people posted:
We made a change in the 85X series wich might prevent your node from starting.
The solution is to update manually both your freenet-ext.jar and
freenet-cvs-snapthot.jar.
You can reach us on irc or on support at freenetproject.org if needed.
NextGen$
PS:
