They probably meant 6 digit and it was a typo. The rest of the article references 6 digits. If it’s just an integer (highly likely) it would go up to 10 digits or roughly 2 billion max users. My old coworkers and I used to joke that hitting INTEGER.MAX_VALUE for your customer ID is a good problem to have
5 digit user ids, yet over 700k users? Im sure they must have gone up to 6 digits
I tried the endpoint. 5 digits always gives you a valid user, 6 stops working after some point.
Unless by “digit” they mean any alphanumeric.
You’ve got a lot of options if you go to a 5 characters with letters.
Which they’d kind of have to with 700k users if it’s 5 characters.
If it’s case insensitive, you’ve got 60,000,000+ combinations, and if case sensitive then 916,000,000+ combinations.
It’s numerical only, but the number doesn’t need leading 0s so anything from 1 to 6 digits might be a valid user ID.
That would be an absolute nightmare to administer lol. Though I guess that tracks.
1, 01, 001, 0001, and 00001 would all be different users
Good point, could easily be hex or some higher base
They probably meant 6 digit and it was a typo. The rest of the article references 6 digits. If it’s just an integer (highly likely) it would go up to 10 digits or roughly 2 billion max users. My old coworkers and I used to joke that hitting
INTEGER.MAX_VALUEfor your customer ID is a good problem to have