On Mon, Jan 15, 2007 at 08:48:33PM -0800, Stuart Robinson wrote: > I'll keep looking around. It might be nice to have a configuration option > that says whether or not to store the raw tokens in the database along > with their associated hash values.
We discussed this at length when the change happened and generally speaking, it was decided that there's generally no good reason to need to know what the original token values are, except for when people are curious, hence the plugin call allowing people to deal with it themselves. > BTW, the reason I'm asking about this stuff is that I'd like to be able to > store the raw and hashed values side by side in the database so that a CGI > script can pull token info from the database (say, the Top 10 spammiest > tokens per individual user). I suppose you could, but why? What are you trying to accomplish other than the curiosity about what the values are? -- Randomly Selected Tagline: "A Young Eel is called this." - Jeopardy Question "What is a baby eel Alex." - Theo's Response
pgprm9YEMNZ2V.pgp
Description: PGP signature
