22:58:34aethscymtym: I don't think urandom is recommended anymore
23:01:53mercourisjI believe the accepted way of getting a random seed is by downloading random++ from npm
23:02:04aethI think getrandom() is the new recommend way in Linux
23:02:25mercourisjthe reason why it will always be something new is because you'll be fulfilling the dependency via NPM, and who knows what it will be
23:02:36scymtymACTION loves how the urandom(4) man page claims that getrandom(2) is the safer alternative and then 50% of that man page is a super-complicated section called "Interruption by a signal handler"
23:02:42rmethe /dev/urandom way is nice because it works on a lot of systems (at least linux/freebsd/osx/solaris-ish)
23:03:41aethWell I can understand why switching to getrandom() right way was probably not a good idea because it was introduced fairly recently. The manpage says kernel 3.17
23:03:59aethkernel.org even shows 2 longterm kernels still supported that have a lower version number!
23:21:21ealfonso"If an ERROR-TEMPLATE-DIRECTORY is set in the current acceptor and the directory contains a file corresponding to HTTP-STATUS-CODE named <code>.html, that file is sent to the client after variable substitution"
1:30:49ealfonsothe hunchentoot problem I was having earlier was not a hunchentoot problem. I forgot to use (return ...) in a loop finally clause