4 ms·

Hash collision?

• capableweb 7y ago
  For sure a hash collision in their content-addressed storage system for images. Probably they take a thumbnail of the image and pass it to a md5 function or something instead of truly making sure there are no duplicate IDs.
  • fortran77 7y ago
    It is a hash collision. I think jef_poskanser's take was correct.
  • OJFord 7y ago
    But why not include the timestamp? How many image uploads can Twitter have within whatever resolution time you'd use? I wouldn't have thought it was that many.
    • capableweb 7y ago
      Including the timestamp defeats the content-addressing. You want to not having to store two duplicate images if they are uploaded at different times.