home.social

#filenames — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #filenames, aggregated by home.social.

fetched live
  1. Uh,, cool! I just realized, I can use the Unicode Symbol U+2044 as a forwards slash in file names. These ⁄ .⁄ ⁄ ⁄ are working with NTFS without causing an issue. This is quite nice, because the regular / / / / slashes just won't work.

    #Hacks #Unicode #Filenames #NTFS #Slash #Windows

  2. I still don't use space in file names because it wan't allowed when I started using computers and I still don't trust it to work 😅

    #Old #Linux #OldMan #ImOld #FileNames
  3. @amoroso @lproven Well, I can think of many ways how to improve #computers. 😉

    karl-voit.at/2017/02/10/evolut
    karl-voit.at/2018/08/25/deskop
    karl-voit.at/2019/10/05/innova
    karl-voit.at/2018/10/17/ted-ne

    Once you've got rid of #filenames, #folders, #applications, ... you will find much room for coming up with something fundamental new. This
    time without adapting humans for the computer but the otherwise round: creating the ultimate digital tool for the humans.

    This can never be reached by an evolutionary process like suggested in the article.

    I disagree with the judgment that we tried hard.

    There's no incentive for a revolution. No one is able to start this process. We're pretty much stuck. 🫩

    This is not the top of the IT industry. We're still in its stone age and made a situation where any fundamental change is a downside somehow. A local optimum but never ever the global one, if you like.

    #PIM #Desktop #DesktopMetaphor

  4. @kaito02 Well, I try to get rid of #NixOS as soon as possible because of the large number of flaws it has according to my use-cases and my perspective. (WIll blog about it.)

    However, this image contains just bullshit arguments.

    For example, what entity defines what #filenames should contain and what not? 🤔

    #Immutability has clear advantages for security reasons alone. (Not that I'd invest the additional effort here.)

    "They have played us for absolute fools" -> who forced you to setup Nix?

  5. Great 5 minute presentation from @jennybryan on how to name files.

    I've been writing code for 40 years and I learned several new ideas.

    #filenames #slug

    youtu.be/ES1LTlnpLMk?feature=s

  6. @pvanb Also, if you DO put a #date in your #filenames but DONT use #ISO8601 date format I super duper especially fucking hate you.

    `CHEQUING_ACCOUNT_123456789_May_29-Jun_30_2020.pdf`

    Are you fucking kidding me? On what planet does that make any sense whatsoever. Just give me

    `CHEQUING_ACCOUNT_123456789_2020_06_30.pdf`

  7. It’s 2023 and #Adobe ’s Creative Cloud can’t #sync files («Unable to sync because the folder name is invalid») with these #characters in #FolderNames or #FileNames

    |
    "
    ?
    <
    >
    /
    \
    *
    :
    . (besides the separating dot before the suffix)
    and a space cannot be used as the final character.

  8. Hmmm...I wouldn't try this, but it has its use cases.

    "Linux 5.2 was released over one year ago and with it, a new feature was added to support optimized case-insensitive file name lookups in the Ext4 filesystem. [...] [T]his seems like a good time as any to take a look on why this was merged, and how to put it to work."

    collabora.com/news-and-blog/bl

    #Linux #FileSystems #FileNames #LinuxKernel #Encodings