[–] 5 points 1 week ago* (1 child)

I'll have missed whether you intended to add these words to the date and time stamps in the file names, or whether you intended to replace them. The former drastically increases permutations and thus lowers the risk at generating collisions, especially at subsecond intervals.

Recently I implemented an idea for this I first saw with Keybase: to generate a security key based on 9 or 10 dreary dull words. Each subsequent word increases the permutation power exponentially, meaning the initial list doesn't even have to be all that long.

How fast do camera shutters shut? How many subzero pictures do they take? Does it differ from one model to the next? And: is your storage system capable of keeping up when you have it rename every photo it receive?

  • source
  • [–] 1 point 1 month ago (1 child)

    How would you do this with SQL?

    And sure, we can carefully choose the names of our SQL stored procedures and input arguments. But inside of a procedure where actions take place and statements are made to achieve those? How easy is it, in your experience, do split off sections into their own procedure and rework their name?

  • source
  • [–] 7 points 1 month ago

    What.

    We change language all the time. We constantly create new words and compounds, and assign new meanings.

    Language is not a pool of never-changing words and meanings. It's alive because we, its users, are.

    And of course language can be managed. Look at Korean.

  • source
  • parent
  • context
  • view more: next ›