You can feed a csPRNG with as few bits as you right. It won't be secure if you seed it but this has no impact on unseeded use (or seeding with a wider seed)
Again breaking valid programs. Now you have to roll your own mktemp for non-regular-files (e.g. fifos).
-
-
you're still talking 1% valid use vs 99% bugs. Usage of mktemp for non-file paths is best left to creating stuff in a separate directory after mkdtemp, btw. This works just fine and is reasonably idiot-proof.
-
Yes, in many cases that's a better solution.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.