Projectfreenet.org runs a horribly outdated mirror of the project's
site, looks at least a couple of years old.
It seems to link to the actual freenet software at the real website, but
info and instructions are very old and could confuse users.
Can anything be done about that?
If the Freenet
Hi,
A few years back I wrote freenet-cards which you can give your friends so they
can easily check your node-ref.
For a long time these lived only on a freesite, but I just pushed them on a
normal website to help spread freenet.
- http://freenetcard.draketo.de/
Please use them as you see
Builds 1234-1236 included several changes to routing that we hope
improved things. Specifically:
- The loop fix: when node A is choosing how to route a request it
received from node B, when considering node C's FOAF locations, it
should ignore locations among C's peers that exactly match B's
On Sat, Sep 19, 2009 at 7:26 AM, Ximin Luo xl...@cam.ac.uk wrote:
I created a new branch (bigint7) which tests the performance of java 7's
BigInteger implementation. can people please benchmark it?
BigInteger use java.util.Arrays.copyOfRange and friends, which are java 6 only.
Matthew Toseland wrote:
> On Saturday 19 September 2009 03:46:27 Ximin Luo wrote:
>> http://github.com/freenet/fred-staging/commit/dea2134ba56462afb0806c5e126306bd0441c5bb
>>
>> Why is this commit necessary? The Java API documentation for
>> BigInteger.toByteArray() says "This representation is
Projectfreenet.org runs a horribly outdated mirror of the project's
site, looks at least a couple of years old.
It seems to link to the actual freenet software at the real website, but
info and instructions are very old and could confuse users.
Can anything be done about that?
If the Freenet
ype: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20090921/37dc022d/attachment.pgp>
Builds 1234-1236 included several changes to routing that we hope
improved things. Specifically:
- The "loop fix": when node A is choosing how to route a request it
received from node B, when considering node C's FOAF locations, it
should ignore locations among C's peers that exactly match B's
