Forgive me... but I just have to say it. You know... in school they tell us to design things on paper *BEFORE* we start coding. I have great success using this philosophy in my professional life. Is there a design document for this thing that defines data types, metafiles, file formats and protocols? Are the developers just "winging it"... designing as they code? If the developers are winging it, they are not behaving very professionally in my opinion. You doom Freenet to a floundering and painful failure with this reckless practice. THINK THINGS OUT AND DESIGN BEFORE YOU START TO CODE Don't screw up a good idea (Freenet) please... I know it is pre 1.0 release. But protocols, data types, metafiles and such should have been solidified and documented before coding started. Another question and subject, could you be pushing responsibilities into the freenet core which are best handled by clients...? Sincerely, Michael Carey -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mathew Ryden Sent: Monday, July 16, 2001 4:52 PM To: [EMAIL PROTECTED] Subject: Re: [freenet-chat] Please archive 0.3 content ----- Original Message ----- From: "Greg Wooledge" <[EMAIL PROTECTED]> > John Goerzen ([EMAIL PROTECTED]) wrote: > > > As an addendum, if 0.4 can speak to an 0.3 node, could people just > > keep up the 0.3 nodes for queries until they get cached by 0.4? > Upside down speak you. > > Anyway, the 0.3 and 0.4 nodes won't talk to each other -- there are > currently 2 different Freenet networks[0], and no compatibility across the > 0.3/0.4 divide. The metadata format has changed. (There's also still > some active debate about the exact 0.4 metadata format -- watch out for > flying "/" and other loose punctuation floating around on the lists.) The main reason why there isn't a salvation effort for 0.3 data is becuase the storables fields (metadata for the entire document) are being changed in such a way as to not only invalidate all old keys, but some of the fields in the storables field as well. 0.3 content cannot surive a simple transfer program to the 0.4 format. > [0] Actually there may be more than that; we don't really know. Some of > the older 0.4 node versions are incompatible with newer 0.4 nodes, so > there may be some isolated micro-Freenets out there that won't talk to > anybody else. Also some of the projects like Espra may have their own > separate Freenets. espra's freenet is actually a subset of the entire freenet. The network of old 0.4 nodes can't actually talk to eachother completely and the network of new nodes is about to die as well for the bleeding edge. > -- > Greg Wooledge | "Truth belongs to everybody." > [EMAIL PROTECTED] | - The Red Hot Chili Peppers > http://wooledge.org/~greg/ | -Mathew _______________________________________________ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat _______________________________________________ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
