[FR] Hashed directory structure?

[ernie]

Please confirm

• [x] I am running the latest version of this plugin

Is your feature request related to a problem? Please describe. This may not end up being a problem, but the flattened directory structure for notes seems like it could cause issues for certain filesystems or sync systems that degrade in performance when directories have a huge number of entries.

Describe the solution you'd like A common solution to this problem is a hashed directory structure -- I imagined that hashing based on the year of note creation would avoid any issues for even the most dedicated of note-writers, and I imagined that it likewise might negate the need for a dedicated daily/weekly directory, as well, provided the filenames are such that they avoid collisions.

Describe alternatives you've considered I've considered just waiting and seeing if this becomes enough of a problem to warrant a change.

Additional context I reviewed the code with the intent to create a pull request that hashed notes by year, but quickly realized the code for following links is fairly hairy and dependent on the flat structure right now, so I didn't have time to pursue.

[lambtho12]

I get that it might be a problem for extremely large directories.

However, using the hashed directory structure may cause issues for many people that work using different tools. For instance, even though Telekasten is my favorite tool to access and edit notes, I also look for them using the note app in my phone when I am on the run (my note directory is synced with Nextcloud). Other people like to use Obsidian as well for instance. Not sure how the hashed directory stuff might collide with that workflow.

An other important thing is that all people (myself included) do not work with a completely flat structure, even though this is against the common Zettelkasten mentality. For instance, in my setup I separate big topics just for the sake of organization:

.
├── engineering
├── finance
├── other
├── persoDevel
├── projects
├── philosophy
├── politics
└── source_notes

So I do not know how that would impact my workflow...

Although, I am definitely not an expert on the matter, I may be wrong. This is just to ensure some basic aspects are not overlooked when considering this FR.