Earlier quoted context omitted.
I guess it was so hot, that the database melted.
I'm hosted on Digital Ocean, and the irony is, I'm literally mid-migration to Ghost from Wordpress — if this had happened a week later this wouldn't have happened. I'm trying to figure out how to upgrade the droplet but being honest, my husband is the one who set all this up for me, so it's going to take me a minute to figure out how to add more bandwidth or whatever.
Yet another hot take on “folders versus tags”
71–80 of 181 posts
Re: Yet another hot take on “folders versus tags”
#72It's simple, it's portable, it's good enough. You could in theory improve it by having multiple views of the same data (let's say you want to save some notes about "Naturalis Historia" - should you put it under "ancient Rome" directory or under"biology"?) for example by using hardlinks but I don't know if there is a way to create a backup on another filesystem that will keep hardlinks as hardlinks (DAR seems promising http://dar.linux.free.fr/doc/Features.html but I have yet to try it).
Re: Yet another hot take on “folders versus tags”
#73I keep my personal notes in an app that I wrote which is backed by SQLite. It resembles a wiki. First, I tried tags. This seemed like a good idea and was a lot of fun at first, but eventually I got _really_ tired of having to curate tags for all of my notes and boy there were a lot of them! It's not something you can just do once either, because every time you update a note you have to remember to change the list of…
Re: Yet another hot take on “folders versus tags”
#74Earlier quoted context omitted.
Agree. They both have a place. I use Zotero to keep track of my references and also just interesting things I find. It uses folders and tags. Fantastic!
Could you describe your Zotero folder & tag strategy? I don’t know where to start with this and it’s a hot mess
Re: Yet another hot take on “folders versus tags”
#75Re: Yet another hot take on “folders versus tags”
#76It should be possible to mimic tags with folders & clever scripting that moves files around according to their "tags". Imagine a command like: tagmv file1 file2 directory1 directory2 -t tag1 tag2 tag3 where it moves the files/directories to something like ~/t/tag1#/tag2#/tag3#/ Or instead of using "#" could use some other special/rare character/unicode to indicate that it is a "tag-directory". The hierarchy of the ta…
Karl seems to have a fancy TUI, I made me a cmdline helper https://codeberg.org/mro/Tagger.
Re: Yet another hot take on “folders versus tags”
#77In other words, folders create boundaries between information, and tags connect across those boundaries.
Re: Yet another hot take on “folders versus tags”
#78Earlier quoted context omitted.
Folders are simple, even if tags can imitate them, they can't replace their structure. Tags are a good fit for items that naturally fall into several categories, like music or books, but not for general file systems.
And yet, folders are tags.
Re: Yet another hot take on “folders versus tags”
#79I keep my personal notes in an app that I wrote which is backed by SQLite. It resembles a wiki. First, I tried tags. This seemed like a good idea and was a lot of fun at first, but eventually I got _really_ tired of having to curate tags for all of my notes and boy there were a lot of them! It's not something you can just do once either, because every time you update a note you have to remember to change the list of…
"How to find stuff" is a space with many solutions to similar looking but subtly different problems.
Re: Yet another hot take on “folders versus tags”
#80Trees/hierarchies ("folders") are for organization, unconstrained graphs/networks ("tags") are for ontologies. Crossing these streams leads to a lot of trouble. When flexible graphs/networks are abused for organizational purposes, you get circular dependencies, spaghetti code, and general dysfunction. Organizations (code or people) need to be easy to navigate. When rigid hierarchies are abused for classification purp…
For example, say you have the following datums with the following tags
apple: plant, Rosaceae, tree, fruit
peach: plant, Rosaceae, tree, fruit
rose: plant, Rosaceae, shrub, flower
dandelion: plant, Asteraceae, herb, flower
carrot: plant, Apiaceae, herb, root
pig: animal, Suidae
You can then try to generate a folder structures that optimizes certain parameters like keeping the average number of children to not too far away from ~6 and/or minimizing the depth of the repo structure or whatever. Depending on how you wanna optimize it, you could end up with a number of structures such as: root
- plant
- tree
- apple
- peach
- herb
- dandelion
- carrot
- rose
- animals
- pig
or root
- Rosaceae
- apple
- peach
- rose
- animal
- pig
- other
- dandelion
- carrot
You can use your imagination to think of better structures or optimization problems, but you get the basic point. We can have tags be our primary classification method and have the organizational structure be an outcome of that.