top | item 27611494 (no title) ktm8 | 4 years ago Just for curiosity, how would YT deal with ID collision ?Edit: Before the scheme change I mean discuss order hn newest Thorrez|4 years ago >base64'ed DES-encrypted primary int64Block ciphers (such as DES) don't collide. If they did there would be no way to decrypt them because a block could be decrypted into multiple valid plaintexts. quantumofalpha|4 years ago Not sure about technical details for that but perhaps something like https://vitess.io/docs/reference/features/vitess-sequences/. Vitess itself is a project that grew out of YouTube's needs to scale and shard their MySQL DB. remram|4 years ago Probably they just roll again. You can even implement that in a stored procedure. root_axis|4 years ago Try again? Just a guess.
Thorrez|4 years ago >base64'ed DES-encrypted primary int64Block ciphers (such as DES) don't collide. If they did there would be no way to decrypt them because a block could be decrypted into multiple valid plaintexts.
quantumofalpha|4 years ago Not sure about technical details for that but perhaps something like https://vitess.io/docs/reference/features/vitess-sequences/. Vitess itself is a project that grew out of YouTube's needs to scale and shard their MySQL DB.
Thorrez|4 years ago
Block ciphers (such as DES) don't collide. If they did there would be no way to decrypt them because a block could be decrypted into multiple valid plaintexts.
quantumofalpha|4 years ago
remram|4 years ago
root_axis|4 years ago