Comment on Windows 11 to add an AI agent that runs in background with access to personal folders, warns of security risk

• enumerator4829@sh.itjust.works ⁨6⁩ ⁨days⁩ ago

  You can now have 128 files in your filesystem.

  …microsoft.com/…/maximum-file-path-limitation?tab…

  source

  • burntbacon@discuss.tchncs.de ⁨5⁩ ⁨days⁩ ago

    I think I could honestly get away with 128 deep paths. I don’t use more than twenty unique folders in my day-to-day computing. It might be difficult to get the various programs on board with my trans porn name for each folder, but that’s what tinkering is for, eh?

    source
  • incompetent@programming.dev ⁨5⁩ ⁨days⁩ ago

    Did you post the wrong link? Yours is about “Maximum Path Length Limitation” and the number 128 doesn’t appear anywhere on that page. The max path length is 256 characters.

    Where did you read that “you can now have 128 files in your filesystem?”

    source

    • enumerator4829@sh.itjust.works ⁨5⁩ ⁨days⁩ ago

      If you want to encode information into only the depth of your recursive identically named folders, you have 128 different depths, one character for the name, one for the slash, per level. Yields about 128 possible levels. Leave one off for the last filename, 127.

      If we want to name our folders something longer than a single character, we can store less files. If we want to store our files on linux, by default we get 4096 characters to play with, so about 2k levels (unless we compile our own linux kernel with PATH_MAX set for this very specific purpose). If we run CIFS we may be able to reach up to 16k levels.

      That was my interpretation of OPs (admittedly bad) idea. Personally, I try to avoid implementing inodes as Church numerals.

      source