> All features listed in "What's New" page are part of Razor2. We had to > switch off Nilsimsa temporarily because of a high rate of collisions. I'm > working on modifications to the algorithm as well as comparing methodology > which will be introduced as a new engine. The ETA is not known, there's a > whole lot of other things I have to divide my time with. When introduced, > the new algorithm will catch polymorphisms that ehash is not already > detecting.
And what of Ephemeral Signatures? Where is this documented in a way that will not lead new users to believe that these features are working and stable? > > Razor V2 seems to be short on documentation, especially that which notes the > > reliability of its components, and long on promises. A little clarification > > would go a long way -- people seem to be more annoyed by inflated promises > > than by useful code in progress. > > That sounds like a very off-handed statement coming from someone who > doesn't even use the software. To operate a service that supports more > than a 100,000 users checking millions of emails every day takes exactly > that: "Daily progress on useful code", most of which is not visible in the > client side software. Hah! Just because I don't use Razor currently doesn't mean that I (a) haven't used Razor in the past, or (b) don't subscribe to and read this list. I did not claim that Razor was not useful code in progress; in fact, I implied both that Razor _is_ useful code in progress, and _does_ make inflated promises according to the web page. How does my usage pattern regarding Razor affect the fact that there seems to be a bit of confusion among some who have posted to this list regarding what features work or don't work? Let me restate my earlier point, in hopefully more clear terms: - Razor is a work in progress, and has features which may or may not currently function as planned. - Razor performs functions which are desirable to a large number of people, and can be located and obtained quite easily. - Most people do not read mailing list archives before installing software; they simply expect the software to work as documented on the web pages. - Most people do not want to invest large amounts of time into avoiding UCE; this is the point of Razor. - Having a highly visible, fairly up-to-date list of known issues and disabled features would greatly reduce the frustration and wasted time involved in learning to use Razor, a product intended to reduce frustration and wasted time. > If you undertook a networked project of that size, > which I assume you haven't, you'd know what I am talking about. Any coding skill or experience I do have has no relation to whether or not features which DO NOT WORK are marked as such on Razor's web page. If you carefully read my earlier post, which I assume you haven't, you'd realize that I made no statements regarding the quality of Razor, but only commented that certain features which do not work are advertised to work on the project's web page. In fact, I'm almost certain that you didn't actually read my post, or hopefully you'd have commented on the state of "Ephemeral Signatures". If, regarding what indication of project status is or is not shown on www.vipul.net, I don't know what you're talking about, that would seem to make two of us. No attempt at starting a pissing match will change that; according to the advertising on www.vipul.net these features are in place. I AM NEW TO RAZOR, THE INTERNET, EMAIL, CODING, ELECTRONIC DEVICES, AND RUNNING WATER. I WALKED INTO A PUBLIC LIBRARY AND ASKED SOMEONE NICELY TO PLEASE LET ME MAKE A FOOL OF MYSELF ONLINE, AND THEY TOLD ME TO POST TO THIS LIST. Now that I've taken away every shred of credibility I might have previously pretended to have, could you stop trying to insult my intelligence and show me where on www.vipul.net it explained that fuzzy matching is not yet in place? You say that use of V1 is deprecated, yet as someone who is new to programming and plumbing, I can't seem to find a list of just what SHOULD work in V2 anywhere on the web pages. That aside, I do appreciate your work, and I do understand how much effort it takes to keep a system such as Razor together, especially when adding new features and running under heavy load. Also, ricochet is quickly becoming my favorite Perl script. Good work. Have a nice day. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
