• @Ricaz@lemmy.world
      link
      fedilink
      English
      212 years ago

      Meanwhile Linux (ext4) users are over here sorting by whatever we want.

      With ctime, mtime and atime it doesn’t matter what you call your files!

      I use Arch btw

      • @Eheran@lemmy.world
        link
        fedilink
        English
        12 years ago

        Sure, but then you need the correct file property or else nothing works? Since it is usually not my job to create files, I depend on companies to do the job right. But I have some bad news there. Example: DJI names the recordings or pictures you take something like DJI0001.jpg. guess what happens after DJI0999.jpg? That’s right, DJI0001.jpg. and don’t get me going about random time jumps in the date recorded/taken embedded in the file. Pure cancer. The script to rename the files to YYYYMMDD_HHMMSS looks like shit because of all the special cases you need to consider.

    • TWeaK
      link
      fedilink
      English
      192 years ago

      Strictly speaking in ISO 8601 it would be 2023-12-31.

    • Zamotic
      link
      fedilink
      English
      102 years ago

      I completely agree. Everyone always asks me why I suffix my filenames with the date like this (or YYYY.MM.DD). But this is so files sure up in correct order when sorted my name. It seems so obvious.

    • @nero@lemmy.world
      link
      fedilink
      English
      12 years ago

      How does that last point work? The ”Putting the date in the files ensures it wouldn’t disappear due to OS shenanigans.”?

      • NessD
        link
        fedilink
        English
        152 years ago

        You create a file on 30.09.2010, back it up and lose it due to hardware failure on 12.07.2022. When you restore the file from your backup to your device it will most likely be stamped as created 12.07.2022 even though originally it was created before that. If you name your file manual_2010-09-30.pdf you always know the date it was created and sort it by that filename.