Conversation

Replying to and
If it becomes problematic when you want to share parts, then it seems like the choice is between making content islands or somehow tagging every single note with who gets to see it. That's too much effort for the writer and will lead to weird voids in what some readers will see.
1
1
Replying to and
yeah tagging every note is a failure mode... that's how Google+ circles model failed miserably. Nobody's got time to do that level of high friction curation. If the graph were a pure DAG, you could tree-level permissioning, but this one isn't
1
4
Replying to and
Dont think so, since you just bias toward privacy when there is ambiguity. Subtree that is shared nested under private tag in a strange loop way? Just don't show I it -- flag why not showed in UI
1
3
Replying to and
Ah but I mean with privacy variations along the way... but your answer sounds fine... conservative privacy should break strange-loop leaks, though it still doesn't solve the high-friction individual page permission-setting problem. I'd like to see how you do tree permissions.
Replying to and
There probably is an elegant solution to this complex problem. In the face of complexity, I would expect users to pick an uglier yet more legible solution, like keeping everything private & screenshotting or exporting bits to Evernote.
1
1