Conversation

What I see as working better is linear plus varying width, so you can read the same but deeper, make each step of the journey simpler or more complex depending on how much you want to invest. (i.e. post X has 3 progressively more complex variants)
2
Yes… but maybe making an explicit conceptual dependency graph (“you can only read this web page if you already understand X, Y, and Z; follow the links for those if you don’t”) is worth a try.
1
1
Amusingly, I disagree with the founder! He clashed w Eliezer, who wanted to focus on specific content, do special-case stuff, perfect that. Alexei thinks they should have focused on getting more authors. Premature in my view: prove in the high-effort case, then generalize.
1
3
It’s sad: in the end, we’re left with no clear insight about what the best-case problems were with that core idea of surfacing and navigating dependency chains.
2
3
I’m reading it now… thank you, extremely interesting, and discouraging. Given your bearishness on the whole space, I’m wondering why you have built, and are actively using, one yourself?
Image
1
1
My goals are very different. My writing system is about helping me think, not about creating a legible communications artifact. The challenges are quite different across the two domains! The classic hypertext problems aren’t so limiting in a writing-focused context.
1
4
Show replies
This Tweet was deleted by the Tweet author. Learn more
Thanks for that, Ryan. There *are* other public working note archives I enjoy. For instance, John Carmack’s .plan files! Even some personal wikis. My hunch is that outliner-oriented writing encourages more atomization by default—hence less coherently-legible-to-others by default.
4