IEEE Computing Covers Freenet
Rayban writes: "From the Freenet Project homepage: IEEE Internet Computing has an article (pdf) entitled 'Protecting Free Expression Online with Freenet.' It provides an excellent technical introduction to the core ideas behind Freenet."
The problem is complexity. The Freenet protocol is more complex by orders of magnitude than protocols such as gnutella, FastTrack, edonkey, etc. Complex software is hard to write. Complex software that cannot be tested before release is almost impossible to write.
Do you believe in death after life?
I've been running a node or two for several years now. There were once a large number of Freenet web sites, but when the protocol changed, most of them dissappeared. Now a lot of them are coming back. But who's to say the protocal won't change again in a few months, and we're back to square one. It seems to be a project with no plan and thus no endpoint. Imagine if Microsoft changed the format for Word files every 6 months, and you get the idea.
The founder guy gave a talk that I had the pleasure of attending this summer.
The coolest thing freenet is used for now: helping free speech in China. There is a version that fits on a floppy and it's used to spread information about things the Communist party doesn't like: basically anything that isn't pro-Communist party.
The funny thing: when pressed on what freenet is used most for, the answer came back: porn. Laughs all around at the talk, but the positive impact in China seems like a good example to me.
"To hold a grudge is to maintain an intense connection with someone you might not want to have a relationship with in the first place."
-Francine Prose
A speech...
-- mikeDOTd
The streets shall flow with the blood of the Guberminky.
Spam is the current problem in frost. There are people, who think that they need more free speech/expression than others and try to spam other groups away.
I'm sure protocols using freenet (in this case Text Over Freenet, which Frost uses) will develop more to a direction where messagers are identified by digital signatures (either with Freenet signatures like SSK-keys, which can be created only by knowing a private key, or by PGP/GPG-like methods) and getting rid of noise/spam is as easy as pressing a button "Show only a message signed by a friend" etc. Trusted keys can also be passed very easily as anyone familiar with keyservers know.
Currently Freenet protocol itself doesn't provide a method to securely pass a message to an SSK-key holder, which can't be read by anyone else.. but the other way aroud works very well. I'm sure this new keytype won't be added to Freenet since it would be another protocol change in the middle of 0.4 development. In 0.6 it could change again.
In Freenet 0.even are development and 0.odd are 'stable' in opposite of Linux Kernel development.
No need for your own web space.
Is there a reason why that "http://crap.js" can't be a "file://crap.js" and reference the js file on the users hard disc?