• 001100 010010@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    90
    arrow-down
    4
    ·
    edit-2
    1 year ago

    Can’t relate. It’s 20231231 for me.

    Edit: Also this format is superior for file sorting. All files are chronological.

    In your time format: 010124 goes before 123123.

    You could have 4 files dated: January 01, 2002; June 11, 2001; July 21, 2004; December 31, 2003

    In your time format the files would be sorted like this:

    010102
    061101
    072104
    123103
    

    It’s 2002, then 2001, then 2004, then 2003. What a fucking mess.

    In ISO 8601, there’s no such issue.

    Before you reply saying theres a sort by date feature, yes I know, but file creation date isn’t the same as when the data is actually recorded. You could be inputting that data from a piece of paper in 2005 after the data being recorded in the years prior, so the creation dates would all be in 2005. Also, sometimes when copying files, the dates randomly reset. Putting the date in the filename ensures it wouldn’t disappear due to OS shenanigans.

    • Ricaz@lemmy.world
      link
      fedilink
      English
      arrow-up
      24
      arrow-down
      2
      ·
      1 year 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
        arrow-up
        1
        ·
        1 year 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.

        • Ricaz@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Oh I agree wholeheartedly, I just wanted to advertise Linux. ISO 8601 for life, baby

    • Zamotic@lemmy.zip
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year 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
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

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

      • NessD@lemmy.world
        link
        fedilink
        English
        arrow-up
        14
        ·
        1 year 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.

      • 001100 010010@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Example:

        Lab_Report_20020101

        That’s what I always do with files. Windows like to reset your date attributes for some reason. If you copy a file, or upload it to cloud and redownload, there are some cloud services that doesn’t save the file date for some reason. Filename always gets saved.