Hi, RC2 was quite promising and not many critical bugs were discovered. Hereby I present you RC3 of Web Of Trust 0.4 / Freetalk 0.1
They use the same identity / message namespace as RC2 - your old RC2 databases will be usable with them. (Notice: They will say "RC2" in some places even though they are RC3 because of that.) Messages/identities of RC1 or before are not visible with RC3. RC3 is a very good candidate for becoming the final soon, the size of the changelog [2] has decreased much. So please, help us with testing the RC3s. Try to use them in any possible way - write many messages, assign trust values - just use all features which you can find. Report anything which does not work. You can also post bug reports / feature suggestions there. You can also send them to FMS, to Freetalk or by mail to xor at freenetproject.org Freetalk or Email is preferred. If you want to provide extended help with testing, please watch your Freenet's log files. Instructions are at the end of this message in [1]. Installation instructions: 1. On the Freenet web interface, go to "Configuration" => "Plugins" 2. In the "Add an Unofficial Plugin" enter the plugin URL and disable the "Local files only" checkbox. 3. Click "Load". 4. After Freetalk is loaded, it will fill the "Forums" menu of the web interface, Web of Trust will give you a "Community" menu URLs: http://downloads.freenetproject.org/alpha/plugins/WebOfTrust/WebOfTrust- version-0.4-RC3.jar http://downloads.freenetproject.org/alpha/plugins/Freetalk/Freetalk- version-0.1-RC3.jar Things you should know: - These release candidates use a different identity namespace than the previously released RC1 and before versions. You will not see any identities / messages from them. Notice that the "Restore an identity" feature will not work because the old identities do not exist within the new namespace. You are free to re-use their SSK/USK URI when creating a new identity however. - The final versions will reset the name space yet once again because the release candidates to not provide auto-update and we do not want outdated versions to pollute the final namespace. This is a minor loss though because it is not intended to have a testing phase longer than a week. - After you post a message, it will treated like a message from someone else in the downloading process. Therefore, it might take ~15-20 minutes until you see your own messages. It is done this way to allow you to notice an error in the uploading process if your own messages are not downloaded at all. Thank you & greetings xor [1] Logging instructions 1. Switch the Freenet web interface to advanced mode (the link for that is at the bottom) 2. Go to Configuration => Logs 3. Set "Minimum priority to log messages at" to "NONE". This will disable all logging which is not explicitly configured in the following step 4. Set "Detailed priority thresholds" to "plugins.Freetalk:ERROR,plugins.WebOfTrust:ERROR". This will enable logging of errors just for Freetalk and WoT. 5. Set "Log rotation interval" to a higher value, "24HOUR" for example 6. Install Freetalk/WoT as described below. 7. After they have been running for some time, go to your Freenet installation directory, there is a folder called "logs", in this folder you can check "freenet-latest.log" for errors and report them. It will be rotated away after the configured rotation interval. Notice that the logs are very likely to contain information which tells us which identities you use and also might even tell us the insert URIs of the identities! 8. Further, Freetalk and WoT do intensive integrity tests after startup, so it might make sense to restart your node at some point and check for errors after Freetalk/WoT have started up, which you can tell by their menus being visible on the web interface of your node [2] Changelogs: Freetalk RC3: - Missed update to Version.java at beginning; update at end. Do not reset namespace. - Fix extractIdFromFreetalkAddress, missing Freetalk.WOT_CONTEXT; apparently this breaks NNTP login. - CSS fix. - Separate deleting a message rating and reverting its effect because the user changed their mind versus deleting it without removing its effect because we are deleting an identity. In the latter case we don't want to undo the effect. - Disallow @ in nicknames. - Database version increment and auto-upgrade to fix nicknames. WoT RC3: - Update Version (missing RC2 at beginning of review period, then RC3 at end). Don't change the namespace. - Add a TODO. - Make IntroductionPuzzle implement Cloneable. ** Doubtful, as our clone() doesn't use super.clone() - Toad. - Implement (Own)IntroductionPuzzle.clone(). (Supporting changes: slight changes to constructors and add getSolver()). - Implement IntroductionPuzzle.equals(). ** Throws if passed a non- IntroductionPuzzle, should return false. - Comments etc. - Indenting. - Improvements to code used by unit tests e.g. alternate constructors. - Implement lots of unit tests for IntroductionPuzzleStore. - Allow changing trust level for identity on the IdentityPage. This includes changing it from any OwnIdentity (shows a list). * Security implications? I guess it can be changed if we eventually decide to have logins? - Add IntroductionPuzzle.hashCode() so can put in a HashSet. - Make IntroductionPuzzleStore.getFreeIndex work for Identity's not just OwnIdentity's. - Better toString(). - Fix not updating mLastChangedDate initially in Trust constructor when parameters are at their default values. - Database version increment and auto-upgrade to fix the previous issue, and the next one. - Disallow @ in nicknames. - Fix collisions during puzzle inserts by aborting the previous lot, which would have collided. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20110323/f4632296/attachment.pgp>
