Conversation

One of the things you're going to run into is people wanting to separate out projects. Currently I'm using it only for 1 project, and I see two different reasons for wanting separate ones: separate "branding" for public things and separate permissions.
2
24
The branding reason I think is a possibly bad one because it creates a tradeoff with the hedgehoggy-second-brain model, which makes me think you should be cautious about building out in the direction of highly polished publishing media with skinning, logos, domain names etc
1
6
But the permissions thing is a good one and doesn't mess with the hedgehog second brain model. I might want to share my book project notes with Alice but not Bob, my science fiction novel attempt with Bob but not Alice, and my personal notes with my wife but no outsiders.
1
4
I'm guessing this is already on your roadmap, but the solution is permission buckets, where everything tagged "multitemporality book" could be given the same permission settings, but with people with access to multiple projects, crosslinks and transclusions still work.
1
5
This will be my bugs/feature requests thread 😆 Want: pseudogarbage collection. Detect orphan empty pages and "collect" them by autolinking them to an auto-generated page called "garbage" whence I can either flesh them out, merge them with something else, or delete
2
21
Want: Starred pages should appear differently (eg color or shape), and with textual annotation, in the graph view. Beyond about 10 nodes it's impossible to maintain the graph-level situation awareness.
2
6
Want: Starred nodes should have persistent repositioned states, so the viz algorithm should take the starred nodes positions as static and draw the rest of the graph around them. I have a feeling this may make the graph viz intractable though.
2
5