@codexeditor @julianweisser @itunpredictable I can tell you I'm hitting one aspect of scale issues: Namespace issues. I use my @RoamResearch for a _lot_ of different projects; I'm Renaissance that way. But how do I tell a character name for a script, a character name for a short story, and a guy that sent me a Tweet aprt?
@codexeditor @julianweisser @itunpredictable @RoamResearch Obviously at query-scale, I look for co-emergent tags that define namespaces. But as straight suggestions as I type? As more data gets poured in, similar lexical things become homogenized. But my thoughts and needs aren't homogeneous.
@codexeditor @julianweisser @itunpredictable @RoamResearch I need tools for differentiating intent beyond the block level, maybe something at the meta-session level, but that's well beyond the scope of the tool as it stands.
@codexeditor @julianweisser @itunpredictable @RoamResearch ("Scope" might be exactly the idea I need. Some way to indicate to the system "I'm working on my ScreenDraught. Now I'm working on game research. Now I'm working on this game design, but this idea might also be useful for my ScreenDraught.")
@codexeditor @julianweisser @itunpredictable @RoamResearch (This kind of problem really only comes up when you have an overloaded process/procedural space for a tool. Other tools differentiate by project/filename. Might be worth thinking about by looking at how #Fusion360 handles assemblies.)
