3 ms·
As a user I don't want to type a 8 symbol random gibberish identifier any more than a 64 symbol one. Don't waste your time with making it less painful, use the
by danbruc 13y ago
As a user I don't want to type a 8 symbol random gibberish identifier any more than a 64 symbol one. Don't waste your time with making it less painful, use the time to avoid this scenario entirely.
- jffry 13y agoAgreed, I would've just base64-encoded a GUID and been done with it, but it was clear that the author nerd-sniped[1] himself and couldn't put it down until he'd come up with a solution. [1] As always, relevant XKCD: http://xkcd.com/356/ http://xkcd.com/356/
- curun1r 13y agoThere's more to ID length concerns than just URL length. Those IDs tend to be IDs in a database which usually need to be indexed. Even packing the 128 bits of a UUID into a binary(16) can make your indexes quite large and make queries with joins surprisingly slow. I think extra effort to go below 64 bits may be a bit unnecessary, getting from 128 to 64 can make a big difference on the back end.