That kind of multiple level directory structure is a common solution to speed up file retrieval when you have to handle a large number of files. A lot of other application use that kind of structure to keep some kind of file cache (e.g. firefox, squid).

Instead of a single large directory with all the files, the application create a structure of subdirectories and uses some rule to choose in which directory to put each file. In this way, it is easier and quicker to find the needed file.

Let's do a simple example: If I want to keep a file for each one of my customers. I'll create a directory for each alphabet letter and then, in each one of these directories, a directory for each alphabet letter. Now I can put "DimitrisTzortzis.info" file in the T/D directory.

From this point, I start to do some supposition based only on my experience, because I do not know the details of dropbox and tomboy implementations.

Usually, to manage a large structure of nested subdirectory is easier than to manage a single large directory (at least, on unix filesystems). This should be true also for dropbox so you do not have to worry about this. That "strange" structure will help dropbox to speed up the things.

Unluckily Tomboy directory structure seems to grow when you create new notes and not to shrink when you delete them. This could explain why your structure is so big with so few notes in it.

That kind of multiple level directory structure is a common solution to speed up file retrieval when you have to handle a large number of files. A lot of other application use that kind of structure to keep some kind of file cache (e.g. firefox, squid).

Instead of a single large directory with all the files, the application create a structure of subdirectories and uses some rule to choose in which directory to put each file. In this way, it is easier and quicker to find the needed file.

Let's do a simple example: If I want to keep a file for each one of my customers. I'll create a directory for each alphabet letter and then, in each one of these directories, a directory for each alphabet letter. Now I can put "DimitrisTzortzis.info" file in the T/D directory.

From this point, I start to do some supposition based only on my experience, because I do not know the details of dropbox and tomboy implementations.

Usually, to manage a large structure of nested subdirectory is easier than to manage a single large directory (at least, on unix filesystems). This should be true also for dropbox so you do not have to worry about this. That "strange" structure will help dropbox to speed up the things.

Unluckily Tomboy directory structure seems to grow when you create new notes and not to shrink when you delete them. This could explain why your structure is so big with so few notes in it.