Hi.
With the new year I've decided to start up something I felt Freenet's
needed, a weekly mail summary, similar to those for the Linux kernel and
various projects at Kernel Cousins (http://kt.zork.net). It'll cover the
devl, support and tech mailing lists. The CVS mailing list doesn't
really lend itself to summary, and the chat and documentation lists seem
dead, and I can't sign up because hawk is apparently dead to me.

This first issue will cover threads from 1/1 to 1/7 - there's obviously
interesting messages from before that, but starting this requires some
cut off point, and doesn't the new year work nicely?

[tech at freenetproject.org]

No messages. The last email seems to have been December 20 of 2002. 

[devl at freenetproject.org]

Subject:        [freenet-dev] Compiling Freenet for the .NET runtime
Date:   01 Jan 2003 09:10:13 +0000

Simon Porter <hailstormxp at fairadsl.co.uk> mentioned his attempts to
compile Freenet for the .NET environment, using Visual Studio and the J#
language. He felt it would provide a performance boost, although Fish
<fish at bovine.artificial-stupidity.net> felt Sun's current JVM would
provide similar performance, and felt that using a free .NET vm like
Mono should be a goal of any .NET development. Robert Bihlmeyer
<robbe at debian.org> was similarly skeptical of speed boosts, and
mentioned goran and gcj native compilation. Ian Clarke
<ian at freenetproject.org> responded to Robert's comment on Simon Porter's
error messages by asking, "Aren't we supposed to be trying not to use
anything that isn't in the 1.1 API/Kaffe?" Matthew Toseland
<toad at amphibian.dyndns.org> responded with "Kaffe implements more than
the 1.1 API."

Subject:        [freenet-dev] New Anonymity Filter
Date:   01 Jan 2003 20:45:19 +0000

Matthew Toseland introduced a new anonymity filter in build 631, which
parses the entire HTML file and passes along only acceptable tags, as a
way to avoid various CSS identity leaking tricks. There was concern
about the limitations, such as lacking CSS support and blocking various
tags, but nothing concrete since the filter was introduced solely in the
development branch. Later, Matthew revealed an updated version capable
of filtering CSS2 properly, again solely in the unstable branch.

Subject:        [freenet-dev] Stuff to do for 0.5.1
Date:   01 Jan 2003 15:11:03 -0800

Ian Clarke mentioned his work with Tiki, a PHP based Wiki, and requested
volunteers and CSS themes.He also mentioned a wish for monthly
subscriptions of donations as opposed to one-time payments. The URL is 
[http://freenetproject.org/tiki/].

Subject:        [freenet-dev] (no subject)
Date:   02 Jan 2003 20:45:27 +0000

Simon Porter gave his thoughts on the proposed new website.
Specifically, he felt the "What is Freenet" section to be the most
important part of the site, and attached a sample. There was a fair
amount of discussion over how to properly explain Freenet to a
non-technical audience. The terms "small-world effect" and
"six-degrees-of-seperation" were bandied about as quick and easy ways.

[support at freenetproject.org]

Subject:        [freenet-support] A new member
Date:   02 Jan 2003 18:12:13 +0200

Catalin <ady982 at ploiesti.astral.ro> introduced themself as someone
interested in ensuring freedom and interested in Freenet, and asked
whether Freenet could allow node runners to see what was stored in their
node and delete offending material. They also mentioned informing
nameless "organizations" about offending material on Freenet, and noted
a lack of response. Matthew Toseland diplomatically (this issue has come
up before, and is discussed on the Freenet site) reminded Catalin that
Freenet by nature is not designed to censor material being passed
between nodes. Catalin agreed, and brought up the browser limitation
problem, where browsers treat Fproxy as a single server and refuse to
open more than X connections, causing pages to freeze until others are
retrieved or fail. Der Vagabund <vagabund at users.sourceforge.net> replied
with a clip from the readme file detailing the solution, and noted it
was not included in the Windows version of Freenet.

Subject:        [freenet-support] Too many builds!
Date:   03 Jan 2003 15:34:15 +0200

Catalin complained about the numerous builds of Freenet, as they had
skipped from 539 to 641 in two days. Ian Clarke reminded him that
upgrading was not mandatory. Catalin then asked how they could find out
what specific bugfixes and improvements were in a build, and Ian pointed
him to the cvs at freenetproject.org mailing list, and Greg Wooledge
<greg at wooledge.org> pointed him to cvs2cl
[http://www.red-bean.com/cvs2cl/].

Subject:        [freenet-support] temp files
Date:   04 Jan 2003 23:33:54 -0800

Joel M. Baldwin <qumqats at outel.org> mentioned that he had found 125MB
worth of files in the Freenet temp directory. Matthew Toseland explained
that it was cleaned out on node startup. Joel felt this was
unacceptable, as long running nodes would fail to be cleaned out, and
thought they should be cleaned every few minutes or hours. He also
thought that the node failed to properly clean out temp on startup as
claimed. [marcoc1 at dada.it] agreed, saying that his various nodes, using
builds 539 to 629) never cleaned out the temp directory, and wished for
secure deletion. Matthew said that 629 was old, and later unstable nodes
should be okay, and that secure deletion was problematic on journaled
filesystems, and almost impossible across platforms. He felt that if it
is a big problem, the data should be encrypted with temporary keys.

This concludes this weekly mail summary of the various Freenet mailing
lists. Hopefully someone will find this useful. Perhaps when the freenet
site stops bugging out it could be added somewhere?
-- 
Aaron Kurtz - GnuPG Key ID ED588CF2 - Use it
Ignore false slogans.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20030109/3f388848/attachment.pgp>

Reply via email to