i'm thinking about what blogging on knov. i imagine it woul…
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...
Replies
There would have to be some kind of visual change that signals "published" content or that makes it more navigable for a reader who is not already actively engaged.
Though the text itself might not have to be different. Alternatively, you could have some kind of overworld map that guides readers into the many streams of a knov area.
Kind of like reading.supply tree explorer.
This visual aspect is structured and simplified compared to the content itself.
This overworld map could mark entry points into the embedded webs of knov threads.
Entry points = existing branches. or useful prompts or queries to search.
The separate channel is a good idea as well. And i like the idea of using !blog to queue up a post. What happens after and how it should look, I'm not sure.
An alternate idea would be to make @ usernames searchable and I could make a tag for my blog and share the link to that knov search.
Or have a thread and use the !blog command to filter the thread but only make that filter visible publicly. But that seems tricky.
I think the public stream idea is good, I'm also thinking about letting you filter the stream on !root vs !branches vs !leaves but having those tags be generate automatically and even making those filters part of the UI
I like the nudge toward structure for when you want there to be structure.
lack of friction can increase flow but sometimes overwhelm it. Constraints provide clarity.
where am I? At the root. What is this a leaf or edge to a larger discussion.