0

I want to do something similar to what YouTube does. For example, this is a valid YouTube video ID didzxUkrtS0

Right now I am storing user's IDs with an integer number, and I want to translate those numbers to a 8 character alphanumerical identification. For example: FZ3EY1IC (not hexadecimal)

I already know that I can implement it with MD5 and then take the first 8 hex numbers, but it doesn't cover the entire alphabet.

What should I do to create a unique pattern using integers, that should never repeat?

ʇsәɹoɈ
  • 22,757
  • 7
  • 55
  • 61
Pacha
  • 1,438
  • 3
  • 23
  • 46
  • Probably this might help http://stackoverflow.com/questions/1051949/map-incrementing-integer-range-to-six-digit-base-26-max-but-unpredictably/1052896#1052896 – galymzhan Apr 16 '13 at 04:37
  • The thing is that if I use only a one digit number (for example 3), it will translate to `c` instead of 8 alphanumeric characters – Pacha Apr 16 '13 at 04:39
  • Did you read the answer carefully? Look at the table at the end of the answer, all IDs map to 6-character unique strings – galymzhan Apr 16 '13 at 04:41
  • @Patashu The same as I said before, I want 8 alphanumeric characters. Base64 will give me only a few if I use only one digit – Pacha Apr 16 '13 at 04:41
  • This might be useful: http://stackoverflow.com/questions/11680176/alphanumeric-hash-a-z-0-9 – Vivek Ghaisas Apr 16 '13 at 04:50

2 Answers2

0

I'm pretty sure what sites like youtube and bitly do is store a big table in the database that translates the alphanumerical identifiers for each link to the internal ID of what they're for (either that or it's stored in the row). And when it needs a new identifier, compute a random one and store it. The reason why you need to do this is so that an attacker cannot predict the ID of the next piece of content to be added.

Patashu
  • 21,443
  • 3
  • 45
  • 53
0

Make your integer 5 8-bit bytes long (by adding a byte with a random value if your integer is 32-bit), that's 40 bits of data.

Cryptographically encrypt the 5 bytes of your integer using some key, which you probably want to keep private.

Slice the 40 encrypted bits into 8 5-bit parts. Encode each part using 32 alphanumeric characters. You may choose to use different 32 (out of the total 36) characters for each part.

The reverse operation is trivial.

Alexey Frunze
  • 61,140
  • 12
  • 83
  • 180