 | | Re: Allocation of member #'s
|
|
(...) Because of URLs that contain them. (...) I've yet to see a username-system that (a) handles collisions in a reasonable way if the usernames are system-assigned, or (b) doesn't lead quickly to garbage if the usernames are user-chosen. --Todd (27 years ago, 3-Jul-99, to lugnet.admin.general)
|
| |
 | | Re: Allocation of member #'s
|
|
(...) Whoops, I think I accidentally didn't not make a double-negative there. --Todd (27 years ago, 3-Jul-99, to lugnet.admin.general)
|
| |
 | | Re: Allocation of member #'s
|
|
(...) Well, if they're still generally increasing slowly and the randomness comes from a small pool of lowest-available numbers rather than a large pool of, say, 32-bit integers, then that would certainly work too. (...) This is something I've been (...) (27 years ago, 3-Jul-99, to lugnet.admin.general)
|
| |
 | | Re: Allocation of member #'s
|
|
(...) Why not just make this whole thing moot and just assign numbers in a random or pseudo-random lottery? Have each person apply for a number, and have a server doohicky spit out a random number from an available pool. I think we're attaching far (...) (27 years ago, 3-Jul-99, to lugnet.admin.general)
|
| |
 | | Re: Allocation of member #'s
|
|
(...) <snip> (...) I have several suggestions: 1) Why not just make the numbers internal to the system so that we never see them. That way we could all be given any old number and the part that we would see would be a username of some sort. I'm sure (...) (27 years ago, 3-Jul-99, to lugnet.admin.general)
|