Good suggestion, thank you.

I changed

Another option, if you don't want to mess with encoding is to run the generated token through md5, which will produce a hash of the randomly generated token that's URL friendly as-is.

to

Another option, if you don't want to mess with encoding is to run the generated token chunk(s) through md5, which produces a 32 character hexadecimal number derived from the randomly generated token that's URL friendly as-is.

At the start of the article I linked MD5 to its Wikipedia article, and in the first function walk through I linked md5 to the PHP function reference. Also, I linked hexadecimal to Tim's new article on base 16.

Do you find this adequate? We do need articles that really explain how md5, sha1 and so on work but I'm wondering if the cryptography series wouldn't be more appropriate. This article could always be updated later on and linked to a local breakdown of the md5 function.

Let me know, and thanks again for the suggestion.

Hi Ben,

Very good points. This has been a common complaint. Frankly, the way I setup that stuff was quite silly. Live and learn, I guess. At any rate, your advice is under-works and before too long CC will be integrated into the site and we'll make it very easy for you to identify the copyright information.

Currently, according to the terms of use you may use the works only for personal use unless the author granted other rights in the article. In the future, the site terms of use will be changed and commercial projects and so on will be addressed. Basically authors will select a CC as you suggested.

If you have anymore questions let me know.