Freenet 0.7 build 986 is now available. Please upgrade. Changelog:
- Fix CSS backgrounds (and other stuff including url()'s).
- Some (minor?) work on freenet.ini persistence.
- Fix problems (metadata-related errors) inserting large files with
filenames.
- Add EarlyEncode option in FCP inserts,
Freenet 0.7 build 986 is now available. Please upgrade. Changelog:
- Fix CSS backgrounds (and other stuff including url()'s).
- Some (minor?) work on freenet.ini persistence.
- Fix problems (metadata-related errors) inserting large files with
filenames.
- Add EarlyEncode option in FCP inserts,
Freenet 0.7 build 985 is now available. The main change in this build is
that it fixes a bug in the CSS filter: Some pages would produce
"Internal Error" messages rather than displaying the cotent of the page.
Please upgrade.
-- next part --
A non-text attachment was
Freenet 0.7 build 985 is now available. The main change in this build is
that it fixes a bug in the CSS filter: Some pages would produce
Internal Error messages rather than displaying the cotent of the page.
Please upgrade.
signature.asc
Description: Digital signature
Freenet 0.7 build 984 is now available. Please upgrade. Changes:
- More fixes for the CSS filter (you can now use identifiers with
underscores in, as long as they don't start with underscore; drop
unknown @thingy's).
- Fix bugs related to 983's changes for URIGenerated and PutFetchable;
Freenet 0.7 build 983 is now available. Please upgrade, and report any
bugs you find.
Changelog:
- Fix a bug in the CSS filter that broke includes and backgrounds.
- Some more work on Statistics.
- Allow a / on the end of the URI when inserting a directory over FCP.
(Fixes some site inserters;
Freenet 0.7 build 982 is now available. Please upgrade. It should be
available through the auto-updater (if that doesn't work please tell
me). It should also be available to the update scripts or from
http://downloads.freenetproject.org/alpha/ .
Changelog:
- Fixed an exploitable bug in the CSS
Freenet 0.7 build 983 is now available. Please upgrade, and report any
bugs you find.
Changelog:
- Fix a bug in the CSS filter that broke includes and backgrounds.
- Some more work on Statistics.
- Allow a / on the end of the URI when inserting a directory over FCP.
(Fixes some site inserters;
Freenet 0.7 build 978 is now available. Please upgrade. Changelog:
- Some (hopefully minor) crypto fixes relating to DSA.
- Some refactoring.
- Fixes to probe requests. (These are a way to probe the keyspace
distribution and the size of the network).
- Better sanity checking for throttle.dat
Freenet 0.7 build 982 is now available. Please upgrade. It should be
available through the auto-updater (if that doesn't work please tell
me). It should also be available to the update scripts or from
http://downloads.freenetproject.org/alpha/ .
Changelog:
- Fixed an exploitable bug in the CSS
Freenet 0.7 build 978 is now available. Please upgrade. Changelog:
- Some (hopefully minor) crypto fixes relating to DSA.
- Some refactoring.
- Fixes to probe requests. (These are a way to probe the keyspace
distribution and the size of the network).
- Better sanity checking for throttle.dat
Freenet 0.7 build 979 is now available. It fixes a bug affecting FCP.
Sorry folks. Please upgrade.
On Wed, Sep 27, 2006 at 11:41:05PM +0100, toad wrote:
Freenet 0.7 build 978 is now available. Please upgrade. Changelog:
- Some (hopefully minor) crypto fixes relating to DSA.
- Some refactoring.
Freenet 0.7 build 977 is now available. This fixes various bugs and
introduces an experimental feature for inserting a frost message from a
NIM-like page (see http://wiki.freenetproject.org/FreenetFINs). This
build is thanks to nextgens, volodya, dbkr, ljn1981, Jogy and me in no
particular order.
Freenet 0.7 build 977 is now available. This fixes various bugs and
introduces an experimental feature for inserting a frost message from a
NIM-like page (see http://wiki.freenetproject.org/FreenetFINs). This
build is thanks to nextgens, volodya, dbkr, ljn1981, Jogy and me in no
particular order.
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 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
Freenet 0.7 build 972 is now available. Please upgrade ASAP. This build
fixes a security bug with the fetch-key box. If you put in
"/www.whatismyip.com", then your browser would go to www.whatismyip.com,
without any warning! (Because we would redirect ?key=/ to
//; now we check that the key
Freenet 0.7 build 972 is now available. Please upgrade ASAP. This build
fixes a security bug with the fetch-key box. If you put in
/www.whatismyip.com, then your browser would go to www.whatismyip.com,
without any warning! (Because we would redirect ?key=/anything to
//anything; now we check that
e: 9/6/2006 10:53:33 AM
> > Subject: Re: [freenet-support] Freenet 0.7 *PLONK*
> >
> > On Tue, 29 Aug 2006, "freenetwork at web.de" wrote:
> > >Don't feed the troll
> > >
> >
> > I am not a troll. 0.7 is in alpha state. It needs to move to
On Wednesday 06 September 2006 21:07, Nicholas Sturm wrote:
> What is "top-post?"
Exactly that... read the netiquette
MK
Sturm wrote:
> >What is "top-post?"
> >
> >
> >> [Original Message]
> >> From: Fake Name
> >> To:
> >> Cc:
> >> Date: 9/6/2006 10:53:33 AM
> >> Subject: Re: [freenet-support] Freenet 0.7 *PLONK*
> >>
>
seland
> To:
> Date: 9/6/2006 5:49:02 PM
> Subject: Top-posting was Re: [freenet-support] Freenet 0.7 *PLONK*
>
> Top-posting has its uses. I sometimes top-post and sometimes reply
> inline.
>
> On Wed, Sep 06, 2006 at 09:41:06PM +0200, Ortwin Regel wrote:
> > H
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
It will but it will take time. You have to remember that 0.5 never did
(afaik).
On 3 Sep 2006 01:22:23 -, Fake Name
wrote:
>
> On Tue, 29 Aug 2006, "freenetwork at web.de" wrote:
> >Don't feed the troll
> >
>
> I am not a troll. 0.7 is in alpha state. It needs to move to Beta state
> with
>> Don't feed the troll
>>
>
> I am not a troll. 0.7 is in alpha state. It needs to move to Beta state
> with open-net
>
> p.s. please don't top-post
Imho with the limited resources it is especially important to prioritise. There
already
exists opennet, it is called 0,5. However, the darknet
On Sun, Sep 03, 2006 at 01:22:23AM -, Fake Name wrote:
> On Tue, 29 Aug 2006, "freenetwork at web.de" wrote:
> >Don't feed the troll
>
> I am not a troll. 0.7 is in alpha state. It needs to move to Beta state
> with open-net
There are many other requirements for beta. For example, we need
On 9/6/06, Nicholas Sturm wrote:
> What is "top-post?"
See my .sig block. Also, note how I responded to your message.
On the other hand, do we care? Are we caring about this?
--Joel
--
It reverses the normal flow of conversation.
> What's wrong with top-posting?
> > Top-posting.
> > >
What is "top-post?"
> [Original Message]
> From: Fake Name
> To:
> Cc:
> Date: 9/6/2006 10:53:33 AM
> Subject: Re: [freenet-support] Freenet 0.7 *PLONK*
>
> On Tue, 29 Aug 2006, "freenetwork at web.de" wrote:
> >Don't feed the troll
> >
On Tue, 29 Aug 2006, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Don't feed the troll
I am not a troll. 0.7 is in alpha state. It needs to move to Beta state
with open-net
p.s. please don't top-post
Freenet 0.7 is nothing more than yet another in a series of Freenet
failures-in-waiting until
On Sun, Sep 03, 2006 at 01:22:23AM -, Fake Name wrote:
On Tue, 29 Aug 2006, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Don't feed the troll
I am not a troll. 0.7 is in alpha state. It needs to move to Beta state
with open-net
There are many other requirements for beta. For example, we
It will but it will take time. You have to remember that 0.5 never did (afaik).On 3 Sep 2006 01:22:23 -, Fake Name
[EMAIL PROTECTED] wrote:On Tue, 29 Aug 2006,
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:Don't feed the trollI am not a troll. 0.7 is in alpha state.It needs to move to Beta state
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 to
Don't feed the troll
I am not a troll. 0.7 is in alpha state. It needs to move to Beta state
with open-net
p.s. please don't top-post
Imho with the limited resources it is especially important to prioritise. There already
exists opennet, it is called 0,5. However, the darknet is
What is top-post?
[Original Message]
From: Fake Name [EMAIL PROTECTED]
To: support@freenetproject.org
Cc: [EMAIL PROTECTED]
Date: 9/6/2006 10:53:33 AM
Subject: Re: [freenet-support] Freenet 0.7 *PLONK*
On Tue, 29 Aug 2006, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Don't feed the troll
On Wednesday 06 September 2006 21:07, Nicholas Sturm wrote:
What is top-post?
Exactly that... read the netiquette
MK
___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at
On 9/6/06, Nicholas Sturm [EMAIL PROTECTED] wrote:
What is top-post?
See my .sig block. Also, note how I responded to your message.
On the other hand, do we care? Are we caring about this?
--Joel
--
It reverses the normal flow of conversation.
What's wrong with top-posting?
Top-posting.
PROTECTED]
Date: 9/6/2006 10:53:33 AM
Subject: Re: [freenet-support] Freenet 0.7 *PLONK*
On Tue, 29 Aug 2006, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Don't feed the troll
I am not a troll. 0.7 is in alpha state. It needs to move to Beta state
with open-net
p.s. please don't top-post
PROTECTED] wrote:
What is top-post?
[Original Message]
From: Fake Name [EMAIL PROTECTED]
To: support@freenetproject.org
Cc: [EMAIL PROTECTED]
Date: 9/6/2006 10:53:33 AM
Subject: Re: [freenet-support] Freenet 0.7 *PLONK*
On Tue, 29 Aug 2006, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote
@freenetproject.org
Date: 9/6/2006 5:49:02 PM
Subject: Top-posting was Re: [freenet-support] Freenet 0.7 *PLONK*
Top-posting has its uses. I sometimes top-post and sometimes reply
inline.
On Wed, Sep 06, 2006 at 09:41:06PM +0200, Ortwin Regel wrote:
He has a problem with you writing above the email
On Tue, 29 Aug 2006, "freenetwork at web.de" wrote:
>Don't feed the troll
>
I am not a troll. 0.7 is in alpha state. It needs to move to Beta state
with open-net
p.s. please don't top-post
>
>>Freenet 0.7 is nothing more than yet another in a series of Freenet
>>failures-in-waiting until it
Freenet 0.7 build 959 is now available. This fixes some nasty bugs in
958, and some older, related bugs. Please upgrade ASAP. If your 958 is
broken then upgrade manually using update.sh/update.cmd. Thank you.
--
Matthew J Toseland - toad at amphibian.dyndns.org
Freenet Project Official Codemonkey
Freenet 0.7 build 958 is now available. Please upgrade and test. 958
(and 957) changes:
- Fix some deadlocks.
- Fix some bugs related to writing freenet.ini (previous builds may
sometimes have written a corrupt freenet.ini)
--
Matthew J Toseland - toad at amphibian.dyndns.org
Freenet Project
Freenet 0.7 build 955 is now available from the auto-updater (soon,
recommended) and the update script. Please upgrade, and report any bugs
you encounter. Major changes:
- Cache all local requests. This fixes one vulnerability (peers may know
for certain what you requested if they do a timing
Freenet 0.7 build 956 is now available. Please upgrade, test, and report
bugs. Changelog:
- Fixed some deadlocks, prevent some possible deadlocks.
- Fix a bug in the content filter relating to CSS and HTML comments.
- Drop the "a new build is available" notification completely from the
version
Freenet 0.7 build 958 is now available. Please upgrade and test. 958
(and 957) changes:
- Fix some deadlocks.
- Fix some bugs related to writing freenet.ini (previous builds may
sometimes have written a corrupt freenet.ini)
--
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official
On Thu, Aug 31, 2006 at 01:12:53PM -0500, GeckoX wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I was in China last year. I was able to create a VPN connection in the US
> with no problem. Most of the web didn't work, even SSL. SSH was completely
> blocked as well, which is why I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was in China last year. I was able to create a VPN connection in the US with
no problem. Most of the web didn't work, even SSL. SSH was completely blocked
as well, which is why I was surprised that I could connect via VPN with no
problems. This
On Thu, Aug 31, 2006 at 01:12:53PM -0500, GeckoX wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was in China last year. I was able to create a VPN connection in the US
with no problem. Most of the web didn't work, even SSL. SSH was completely
blocked as well, which is why I was
Meh...depends where you're at. It's not one giant firewallit's a
regional thing. Beijing must just have high security. Seems odd that
they'd block out SSHbut I suppose SSH is a good way to hide what
you're doing.
On 9/1/06, Matthew Toseland [EMAIL PROTECTED] wrote:
On Thu, Aug 31, 2006
Freenet 0.7 build 956 is now available. Please upgrade, test, and report
bugs. Changelog:
- Fixed some deadlocks, prevent some possible deadlocks.
- Fix a bug in the content filter relating to CSS and HTML comments.
- Drop the a new build is available notification completely from the
version
Freenet 0.7 build 955 is now available from the auto-updater (soon,
recommended) and the update script. Please upgrade, and report any bugs
you encounter. Major changes:
- Cache all local requests. This fixes one vulnerability (peers may know
for certain what you requested if they do a timing
Matthew Toseland wrote:
> It's unnecessary anyway because it only applies to TCP. It does however
> tell us something very interesting and useful: The firewall is stateless !!
heh, it would be damn expensive to do that in a stateful way.
let's see:
>1. Timing.
>2. Packet size.
>3. It's not a
On 08/31, Matthew Toseland wrote:
> > > Have you thought about that ignoring reset packets thing that was
> > > shown to make it possible to bypass The Great Firewall? I mean, I
> > > don't know too much about it, or if it'd be possible for
> > > freenetbut it might be worth looking in to.
> >
On Thu, Aug 31, 2006 at 06:01:45PM +0400, Roman V. Isaev wrote:
> On 08/31, Matthew Toseland wrote:
> > > > Have you thought about that ignoring reset packets thing that was
> > > > shown to make it possible to bypass The Great Firewall? I mean, I
> > > > don't know too much about it, or if it'd
On Wed, Aug 30, 2006 at 11:52:23PM +0200, David 'Bombe' Roden wrote:
> On Wednesday 30 August 2006 23:47, urza9814 at gmail.com wrote:
>
> > Have you thought about that ignoring reset packets thing that was
> > shown to make it possible to bypass The Great Firewall? I mean, I
> > don't know too
Hundreds of projects? Such as? None of them comes anywhere near to our
techology; most of them are either easily harvestable and blockable
proxy networks, or WASTE clones.
On Wed, Aug 30, 2006 at 05:47:43PM -0400, urza9814 at gmail.com wrote:
> Have you thought about that ignoring reset packets
0.7 has no predictable or repeated bytes whatsoever. It can probably be
identified by several more expensive, less reliable techiques at present:
1. Timing.
2. Packet size.
3. It's not a known protocol, therefore it must be bad.
4. Flow analysis.
On Wed, Aug 30, 2006 at 10:35:32PM +0200, inverse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was in China last year. I was able to create a VPN connection in the US with
no problem. Most of the web didn't work, even SSL. SSH was completely blocked
as well, which is why I was surprised that I could connect via VPN with no
problems. This
urza9814 at gmail.com wrote:
> Have you thought about that ignoring reset packets thing that was
> shown to make it possible to bypass The Great Firewall? I mean, I
> don't know too much about it, or if it'd be possible for
> freenetbut it might be worth looking in to.
it's possible to do
David 'Bombe' Roden wrote:
> Communication between 0.7 nodes doesn't have to exchange public keys,
> those are already known as they are contained in the node reference.
nice!
I definitely need to install 0.7 and capture some packets for testing
On Wednesday 30 August 2006 23:47, urza9814 at gmail.com wrote:
> Have you thought about that ignoring reset packets thing that was
> shown to make it possible to bypass The Great Firewall? I mean, I
> don't know too much about it, or if it'd be possible for
> freenetbut it might be worth
On Wednesday 30 August 2006 22:35, inverse wrote:
> beyond harvesting the connected IP addresses to raid their owner's
> homes, one big concern with encrypted protocols is that they can be
> filtered out by application-level scanning firewalls. I think this is
> exactly what's happening in China.
0.7 has no predictable or repeated bytes whatsoever. It can probably be
identified by several more expensive, less reliable techiques at present:
1. Timing.
2. Packet size.
3. It's not a known protocol, therefore it must be bad.
4. Flow analysis.
On Wed, Aug 30, 2006 at 10:35:32PM +0200, inverse
Hundreds of projects? Such as? None of them comes anywhere near to our
techology; most of them are either easily harvestable and blockable
proxy networks, or WASTE clones.
On Wed, Aug 30, 2006 at 05:47:43PM -0400, [EMAIL PROTECTED] wrote:
Have you thought about that ignoring reset packets thing
On Wed, Aug 30, 2006 at 11:52:23PM +0200, David 'Bombe' Roden wrote:
On Wednesday 30 August 2006 23:47, [EMAIL PROTECTED] wrote:
Have you thought about that ignoring reset packets thing that was
shown to make it possible to bypass The Great Firewall? I mean, I
don't know too much about
On 08/31, Matthew Toseland wrote:
Have you thought about that ignoring reset packets thing that was
shown to make it possible to bypass The Great Firewall? I mean, I
don't know too much about it, or if it'd be possible for
freenetbut it might be worth looking in to.
That would
On Thu, Aug 31, 2006 at 06:01:45PM +0400, Roman V. Isaev wrote:
On 08/31, Matthew Toseland wrote:
Have you thought about that ignoring reset packets thing that was
shown to make it possible to bypass The Great Firewall? I mean, I
don't know too much about it, or if it'd be possible
Matthew Toseland wrote:
It's unnecessary anyway because it only applies to TCP. It does however
tell us something very interesting and useful: The firewall is stateless !!
heh, it would be damn expensive to do that in a stateful way.
let's see:
1. Timing.
2. Packet size.
3. It's not a known
Matthew Toseland wrote:
> Well on the most trivial level, 0.5 doesn't work in china.
>
yo,
beyond harvesting the connected IP addresses to raid their owner's
homes, one big concern with encrypted protocols is that they can be
filtered out by application-level scanning firewalls. I think this
It wasn't safe enough, though, I suppose.
On 30 Aug 2006 03:27:04 -, Crash at remailer-debian.panta-rhei.eu.org <
Crash at remailer-debian.panta-rhei.eu.org> wrote:
>
> On Tue, 29 Aug 2006 22:01:06 +0100, you wrote:
> >
> > Freenet 0.5 had opennet, and yet it was a failure.
> >
>
> Ok, I
Well on the most trivial level, 0.5 doesn't work in china.
On Wed, Aug 30, 2006 at 08:51:32PM +0200, Ortwin Regel wrote:
> It wasn't safe enough, though, I suppose.
>
> On 30 Aug 2006 03:27:04 -, Crash at remailer-debian.panta-rhei.eu.org <
> Crash at remailer-debian.panta-rhei.eu.org>
Have you thought about that ignoring reset packets thing that was
shown to make it possible to bypass The Great Firewall? I mean, I
don't know too much about it, or if it'd be possible for
freenetbut it might be worth looking in to.
Also just wanna add that I fully support the desire to help
On Tue, 29 Aug 2006 22:01:06 +0100, you wrote:
>
> Freenet 0.5 had opennet, and yet it was a failure.
>
Ok, I gotta know this. How is 0.5 considered a failure. I use it daily and
it works flawlessly, Frost messages flow as well as ever, as do downloads of
splitfiles. Yesterday I retrieved a
On Tue, 29 Aug 2006 22:01:06 +0100, you wrote:
Freenet 0.5 had opennet, and yet it was a failure.
Ok, I gotta know this. How is 0.5 considered a failure. I use it daily and
it works flawlessly, Frost messages flow as well as ever, as do downloads of
splitfiles. Yesterday I retrieved a
It wasn't safe enough, though, I suppose.On 30 Aug 2006 03:27:04 -, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
On Tue, 29 Aug 2006 22:01:06 +0100, you wrote: Freenet 0.5 had opennet, and yet it was a failure.Ok, I gotta know this.How is 0.5 considered a failure. I use it daily andit works
Well on the most trivial level, 0.5 doesn't work in china.
On Wed, Aug 30, 2006 at 08:51:32PM +0200, Ortwin Regel wrote:
It wasn't safe enough, though, I suppose.
On 30 Aug 2006 03:27:04 -, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
On Tue, 29 Aug 2006 22:01:06 +0100, you wrote:
Matthew Toseland wrote:
Well on the most trivial level, 0.5 doesn't work in china.
yo,
beyond harvesting the connected IP addresses to raid their owner's
homes, one big concern with encrypted protocols is that they can be
filtered out by application-level scanning firewalls. I think this
On Wednesday 30 August 2006 22:35, inverse wrote:
beyond harvesting the connected IP addresses to raid their owner's
homes, one big concern with encrypted protocols is that they can be
filtered out by application-level scanning firewalls. I think this is
exactly what's happening in China.
Have you thought about that ignoring reset packets thing that was
shown to make it possible to bypass The Great Firewall? I mean, I
don't know too much about it, or if it'd be possible for
freenetbut it might be worth looking in to.
Also just wanna add that I fully support the desire to help
On Wednesday 30 August 2006 23:47, [EMAIL PROTECTED] wrote:
Have you thought about that ignoring reset packets thing that was
shown to make it possible to bypass The Great Firewall? I mean, I
don't know too much about it, or if it'd be possible for
freenetbut it might be worth looking in
David 'Bombe' Roden wrote:
Communication between 0.7 nodes doesn't have to exchange public keys,
those are already known as they are contained in the node reference.
nice!
I definitely need to install 0.7 and capture some packets for testing
___
[EMAIL PROTECTED] wrote:
Have you thought about that ignoring reset packets thing that was
shown to make it possible to bypass The Great Firewall? I mean, I
don't know too much about it, or if it'd be possible for
freenetbut it might be worth looking in to.
it's possible to do it, but
Don't feed the troll
>Freenet 0.7 is nothing more than yet another in a series of Freenet
>failures-in-waiting until it proves itself, IMHO, by emerging out of alpha
>with open-net.
>
>
>___
>Support mailing list
>Support at freenetproject.org
Freenet 0.7 is nothing more than yet another in a series of Freenet
failures-in-waiting until it proves itself, IMHO, by emerging out of alpha
with open-net.
Don't feed the troll
Freenet 0.7 is nothing more than yet another in a series of Freenet
failures-in-waiting until it proves itself, IMHO, by emerging out of alpha
with open-net.
___
Support mailing list
Support@freenetproject.org
Freenet 0.7 is nothing more than yet another in a series of Freenet
failures-in-waiting until it proves itself, IMHO, by emerging out of alpha
with open-net.
___
Support mailing list
Support@freenetproject.org
Freenet 0.7 is nothing more than yet another in a series of Freenet
failures-in-waiting until it proves itself, IMHO, by emerging out of alpha
with open-net.
Freenet 0.7 is nothing more than yet another in a series of Freenet
failures-in-waiting until it proves itself, IMHO, by emerging out of alpha
with open-net.
___
Support mailing list
Support@freenetproject.org
Freenet 0.7 build 953 is now available. It should be deployed through
the auto-updater very soon, and it is already downloadable through the
update scripts. Please upgrade. Changelogs:
953:
- Probably fix insert resuming (again!!)
- Turn off aggressiveGC for now
- Restart non-global persistent
Freenet 0.7 build 953 is now available. It should be deployed through
the auto-updater very soon, and it is already downloadable through the
update scripts. Please upgrade. Changelogs:
953:
- Probably fix insert resuming (again!!)
- Turn off aggressiveGC for now
- Restart non-global persistent
Freenet 0.7 build 950 is now available. Please upgrade, test, report
bugs. The major change in this build is that backoff is no longer a load
limiting as well as a load balancing mechanism: If all a node's peers
are backed off then it will send requests to backed off peers. We have a
separate load
Freenet 0.7 build 949 is now available. This build, and 948, fix various
bugs and introduce some minor new features:
- Fixes to the auto-updater
- Fixes to USK background fetching
- Much faster insert resuming on startup
- STUN wasn't working; is now fixed
- Bombe has provided a way to access
Freenet 0.7 build 950 is now available. Please upgrade, test, report
bugs. The major change in this build is that backoff is no longer a load
limiting as well as a load balancing mechanism: If all a node's peers
are backed off then it will send requests to backed off peers. We have a
separate load
0.7 is the official, maintained version of freenet. It's what you get
when you download freenet from the website. It has, at least, several
hundred nodes. And we simply cannot implement opennet at this point. It
is important that we implement opennet, but not yet, because there are
serious
Freenet build 947 is now available. This build simply makes 944
mandatory as of midnight GMT on Monday (the 21st). This is important
because of various relatively minor changes in recent builds to load
balancing and the lower layers of Freenet: making load limiting data
persistent, increasing
reenet 0.7 build 946 is now available. This, and immediately prior
builds, feature various bugfixes (mostly related to inserts) and some
minor features. Please upgrade and test. Hopefully inserts will work
now...
--
Matthew J Toseland - toad at amphibian.dyndns.org
Freenet Project Official
Freenet 0.7 build 949 is now available. This build, and 948, fix various
bugs and introduce some minor new features:
- Fixes to the auto-updater
- Fixes to USK background fetching
- Much faster insert resuming on startup
- STUN wasn't working; is now fixed
- Bombe has provided a way to access
You really ought to get a second mailing list for the 0.7 network.
Because I'm pretty sure no one here cares until there's an opennet.
On 8/16/06, Matthew Toseland wrote:
> Freenet build 947 is now available. This build simply makes 944
> mandatory as of midnight GMT on Monday (the 21st). This
reenet 0.7 build 946 is now available. This, and immediately prior
builds, feature various bugfixes (mostly related to inserts) and some
minor features. Please upgrade and test. Hopefully inserts will work
now...
--
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey -
Freenet build 947 is now available. This build simply makes 944
mandatory as of midnight GMT on Monday (the 21st). This is important
because of various relatively minor changes in recent builds to load
balancing and the lower layers of Freenet: making load limiting data
persistent, increasing
401 - 500 of 552 matches
Mail list logo
