Meta: Does anyone else feel that tags like memory.corrupted are an overuse of hierarchical tagging? I would much rather see corrupted memory. The odds that someone else thinks to tag this specific...
Meta: Does anyone else feel that tags like memory.corrupted are an overuse of hierarchical tagging? I would much rather see corrupted memory. The odds that someone else thinks to tag this specific thing in this specific hierarchy are low. With geography the hierarchy is more obvious and the odds of alignment between random users is really high. Almost anything else can be tagged hierarchically - data_system.flight. Basically I'm arguing against abstraction. As they say - better to have no abstraction than the wrong abstraction.
"Flight data system" is an actual term being use by NASA, with its own acronym (FDS). FDS is the name given to the onboard computers which handle flight data. It's not a sub-category of a data...
"Flight data system" is an actual term being use by NASA, with its own acronym (FDS). FDS is the name given to the onboard computers which handle flight data. It's not a sub-category of a data system, which is its own separate and unrelated thing. That's why it got written in the tags as a whole.
Whereas "corrupted memory" is directly related to computer memory, which already exists as its own tag (E.g. ~tech?tag=memory and ~comp?tag=memory). So IMO it makes more sense that it should show up when looking at the memory tags, which is why I made it hierarchical. That was my reason for doing that, anyways.
If you think it's a step too far, I can remove the .corrupted, but I personally don't think corrupted_memory should be its own unique tag.
Sure. That sounds better. Changed. cc: @teaearlgraycold Although Tildes search utilizes synonyms, so corrupted = corruption, and even before changing the tag this topic still showed up when...
Although Tildes search utilizes synonyms, so corrupted = corruption, and even before changing the tag this topic still showed up when searching for "memory corruption". And even after the tag was changed to memory.corruption, searching for "corrupted memory" still brings this topic up too.
BTW, assisting the search is one of the main reasons I put so much effort into tagging. That, and I enjoy the process. But people being able to manually browse the tags for related topics is another consideration too, which is why I make use of the hierarchy when it's appropriate.
Meta: Does anyone else feel that tags like
memory.corruptedare an overuse of hierarchical tagging? I would much rather seecorrupted memory. The odds that someone else thinks to tag this specific thing in this specific hierarchy are low. With geography the hierarchy is more obvious and the odds of alignment between random users is really high. Almost anything else can be tagged hierarchically -data_system.flight. Basically I'm arguing against abstraction. As they say - better to have no abstraction than the wrong abstraction."Flight data system" is an actual term being use by NASA, with its own acronym (FDS). FDS is the name given to the onboard computers which handle flight data. It's not a sub-category of a data system, which is its own separate and unrelated thing. That's why it got written in the tags as a whole.
Whereas "corrupted memory" is directly related to computer memory, which already exists as its own tag (E.g. ~tech?tag=memory and ~comp?tag=memory). So IMO it makes more sense that it should show up when looking at the memory tags, which is why I made it hierarchical. That was my reason for doing that, anyways.
If you think it's a step too far, I can remove the .corrupted, but I personally don't think corrupted_memory should be its own unique tag.
Maybe memory.corruption? That seems more likely to be typed in for a variety of purposes, from rowhammer-type attacks to cosmic rays to software bugs.
Sure. That sounds better. Changed. cc: @teaearlgraycold
Although Tildes search utilizes synonyms, so corrupted = corruption, and even before changing the tag this topic still showed up when searching for "memory corruption". And even after the tag was changed to memory.corruption, searching for "corrupted memory" still brings this topic up too.
BTW, assisting the search is one of the main reasons I put so much effort into tagging. That, and I enjoy the process. But people being able to manually browse the tags for related topics is another consideration too, which is why I make use of the hierarchy when it's appropriate.