News for hackers. Stuff that matters.
Re:Foobar by brserc on Tuesday November 11, 2014 @12:52PM (#8591146)
I haven't been able to solve the puzzle - if there's any, however there is some interesting pattern in filenames.

/staticfiles/svg/error.33ab1eb5.svg -> 33ab1eb5 hexadecimal is 866852533, which seems to be a prime number.

I believe the probability is very low if unintended. Also other file names, can be factored more or less to 1 big prime number and few small primes.

Re:Foobar by robryk on Tuesday November 11, 2014 @01:52PM (#8591478)
These hex strings are beginnings of md5 checksums of these files:

   sh-4.3$ md5sum error.33ab1eb5.svg 
   33ab1eb5129ee5085793166d2f691dae  error.33ab1eb5.svg
I believe the point of appending them to the name is a kind of versioning: one'd want to be able to change these files and cause everyone to drop their cached version. This way when one changes a file, the filename changes too (most likely), so the cached old version will not be used.
Re:Foobar by slig on Tuesday November 11, 2014 @03:44PM (#8592049)
You're correct.

It looks like they're using Django. You can configure it to add the md5 of static files to each name. [1]

[1] https://docs.djangoproject.com/en/1.7/ref/contrib/staticfile...

Re:Foobar by brserc on Tuesday November 11, 2014 @02:11PM (#8591575)
Thanks for the explanation!
Re:Foobar by imacomputer2 on Tuesday November 11, 2014 @02:25PM (#8591641)
Have you ever seen the movie PI? You sound like Max, the main character.
Re:Foobar by axg on Tuesday November 11, 2014 @12:58PM (#8591174)
The pattern is they're all hex, we need a cryptographer. The three numbers are

e6cf5ce7 67a53a45 5252068f