Earlier quoted context omitted.
An interesting hybrid approach I've experimented with in the past is to use tags while ensuring that the tags themselves are purely hierarchical. (Is there a name for this scheme?)
I'm not sure of a name, but Tiddlywiki does this. You create hierarchies by having tags by creating an item with the tag as its name which causes all items with said tag to be a child of that item. This has a nice side effect of allowing items to exist in multiple locations (so no unique parent is enforced) while still requiring the graph to be acyclic. It ends up working kind of like hard links for folders/files, bu…
Yet another hot take on “folders versus tags”
171–180 of 181 posts
Re: Yet another hot take on “folders versus tags”
#172Earlier quoted context omitted.
As a node in a tree hierarchy any folder can only have one parent folder. Tags of course allow nodes to have any number of parents (aka "associations"). The relationship between arbitrary nodes in a tree can be determined by tracing their common ancestry, but tags don't provide equivalent functionality, unless you strictly define how tags themselves relate to other tags. An obvious way to do so is to prescribe that e…
> Similar to symlinks, but arguably less hacky, because there is no differentiation between "actual" location and "linked" location. In other words, similar to hardlinks
Minor detail: I intended for different deletion semantics from hardlinks. Whereas hardlinks use reference counting for that (only the last deletion actually deletes); for my purposes, delete anywhere meant delete everywhere.
Re: Yet another hot take on “folders versus tags”
#173Earlier quoted context omitted.
I don't think that would scale. The nested directory structure could reach a depth equivalent to the number of tags to support all combinations. Meanwhile with symlinks you only need one folder per tag and it can be comfortably used with file browsers.
If there was a limit of 10 tags per file, then the max depth would be 10 folders.
Re: Yet another hot take on “folders versus tags”
#174I 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…
Search works brilliantly for your own notes because you know what you're looking for. You wrote the notes. It fails for problems that you can't describe well though, especially if you don't know the technical jargon to search for. Directories and tags can work for that problem because you can easily see relationships like a hierarchy of folders, or what other tags a tagged item has. Tags and folders also act as a pro…
HA! In my case I wrote my notes, but don’t remember what’s in ‘em. It’s endemic for learning.
folders/tags is a false dichotomy.
Re: Yet another hot take on “folders versus tags”
#175Re: Yet another hot take on “folders versus tags”
#176Earlier quoted context omitted.
not sure i follow. can you give an example how exclusion works? all i see is that without using symlinks i can have only one folder/tag per item. i can choose to do that with tags too if i want, but i don't see how using folders helps with that other than forcing me to do it.
If you can nest folders, then a thing is all of its parent folders in addition to the folder it is directly contained in. This is the AND relationship, which you don't get with most tagging systems. To highlight exclusion, consider an example- folder Animals with subfolders Cats and Dogs. A thing can be either a cat or a dog, but not both.
if an object has five tags, it is all those things. that looks like an AND relationship to me.
the rest is search. if your tagging system only does OR searches, then that's indeed a problem, but of the implementation, not of the concept.
and there is no reason both can't coexist.
one application that i use extensively is kphotalbum. it allows me to organize photos by tags, categories, date, folders and other attributes all at the same time. i can navigate and search photos based on all of those attributes. usually i drill down a folder, and then pick tags from within that folder, or i pick tags at the the top level and then work with the folder structure of the selected images. ironically, kphotoalbum does not do well on OR relationships or exclusion of specific attributes. i often use temporary tags to help me there, which kphotoalbum makes trivially easy to use
Re: Yet another hot take on “folders versus tags”
#177Earlier quoted context omitted.
An interesting hybrid approach I've experimented with in the past is to use tags while ensuring that the tags themselves are purely hierarchical. (Is there a name for this scheme?)
Forever ago I built something similar for generating canonical urls for SEO from a tag system (and to concentrate "google juice" from linking), though hierarchies were not strictly enforced. "expert/american" and "american/expert" couldn't have duplicate content so you take your tag system and overlay hierarchies. Anything that wasn't manually set was auto hierarchied based on highest traffic volume. I also prevented…
Re: Yet another hot take on “folders versus tags”
#178Earlier quoted context omitted.
Forever ago I built something similar for generating canonical urls for SEO from a tag system (and to concentrate "google juice" from linking), though hierarchies were not strictly enforced. "expert/american" and "american/expert" couldn't have duplicate content so you take your tag system and overlay hierarchies. Anything that wasn't manually set was auto hierarchied based on highest traffic volume. I also prevented…
Didn't google punish your site for having duplicate entries under different urls?
That was the point of labeling 1 version of any duplicated permutation "canonical", to prevent duplicate content penalties.
https://developers.google.com/search/docs/advanced/crawling/...
Re: Yet another hot take on “folders versus tags”
#179> Sometimes people will ask me what I do when I have something that could go into multiple places and the answer has always been pretty simple: if something could conceivably fit in two different folders I need to consolidate my folders. How does that not lead to an end result where you have one folder "everything", and thus no organization at all? There's always edge cases.
I've got over 2k files in my Obsidian vault and haven't had a problem really. I think it depends on how you categorize things? I'm never going to confuse my tax documents with my short fiction, or my character profiles for a fantasy character for my daily notes page.
Re: Yet another hot take on “folders versus tags”
#180After the past 5 years or so of experiencing the supposed best "folderless" computing has to offer on iOS and ideologically similar platforms. I've gained huge respect for how beautiful the concept of the folder is.
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.
With folders it’s just copy the base folder.
Now I know as devs some of us would suggest version control as the solution but keep in mind with folders my non-technical 70 year old dad can do this action and understand it completely because of the tactility a folder provides.