After an extended discussion on IRC, SomeDude responded: ======================================================= First, thank you TheSeeker and Tommy[D] for your rational arguments.
I'm completely taken aback by toad's belligerent attitude and personal attack against me. Berating someone's intelligence isn't very becoming. I'm also surprised he would like to have an argument with me rather than a conversation. I have no interest in arguing with anyone as I'd much rather has a conversation. I find it humorous that toad says that FMS should have been reviewed had he known at the time how long developing Freetalk was going to take. The next step should be completely obvious. Set a reasonable deadline that Freetalk must be completed by. If it it not completed to satisfaction by this date, start the review of the current FMS implementation. Otherwise the lesson that should have been learned wasn't, and time is just wasting away. As seen on the other thread about a Java FMS implementation, I would support someone developing such a clone. We can work to separate the trust system from the message system so that it could be used by other applications. Before any major investment in time, however, I would want to have a guarantee that if the trust system was separated, and a node plugin developed for FMS and the trust system, that they would be fairly reviewed in an unbiased manner for inclusion in the official plugins list regardless of the existing of any other similar plugins. ======================================================= p0s is of the view that completing FMS to the point where it could be bundled is much less work than either reviewing FMS (which I would have considerable difficulty with on past experience, it's a lot of code and some of it is old hard to review low level C code that has had e.g. format string vulnerabilities), or cloning it in a new plugin. Hopefully Freetalk will be done soon. If it is not we should reconsider. Bundling FMS would be problematic on a practical level - in that we'd have to bundle binaries for multiple platforms (requiring building them), figure out how to update them, and have them run as daemons as Fred does - but the main issue is that the code would need to be reviewed. p0s has agreed to complete writing a spec after Freetalk works reasonably well. Currently there is this: http://wiki.freenetproject.org/Freetalk -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20100412/9f981219/attachment.pgp>
