How would you blog on knovigator?

What is the basic unit of knovigator? That is to say, if I blogged on knov, would it make sense for each card to be a sentence, a couple sentences, a paragraph, or a whole post?

Also how would you map relations differently. Collecting links for a query to solve a research problem is different than deliberately presenting them to a reader.

How would map trees?

see also "learning with @knovigator"

externalization of thought in motion #user_feedback

In the above scenario, each knov card would be a container of a stable post somewhere else on the web.

i'm thinking about what blogging on knov. i imagine it would be a publishing channel similar to how we publish in twitter, and that maybe there is a !blog command that alters the authoring experience. im curious about how you envision it in your ideal world, if at all...

Another way of thinking about knov is as a multi-dimensional conversation. Here are some ideas around that which really resonate with me in the form of a cool comic http://a9.io/glue-comic/

I've been trying to render a knov thread as a "blog" in an experiment. This has been cool because at any point I can create a new thread and quote material from the first thread to let my blog naturally evolve with my thinking over time.

But is this too "old blog"? If knovigator is about search, then is using a thread like a page for a blog the right move?

instead, should it be something more like a search for hungrybreadelevator + blog?

though there is a gap here between where our thinking on this can evolve and where everybody else's expectations are at (audience-wise)

I'm thinking about using the email feature of a stream to update a la substack style, but I feel like daily is too often. If I make a new stream for the hungybreadblog could we tweak it to weekly?

maybe blogs in knov are root threads... and/or each user gets a blog stream by default