so, the question here is should the quests map 1 to 1 to th…
so, the question here is should the quests map 1 to 1 to the twitter thread. if the answer is yes, then you wouldn't be able to edit your quest anymore...
Replies
I don't think the quest should map 1-1 to twitter. What's going on in the thinking and writing on knovigator is different from twitter. There's a different relationship to data/development of thought and socially they are different communities that we cultivate in each.
i have to find people who are interested in this kind of structure
who wants to write in multiple dimensions?
On twitter workflow and how knovigator works with twitter. Twitter itself is a social thinking tool (not just a publishing tool) so we need a way to theorize not just the relationship from knovigator to twitter but twitter back to knovigator.
codon
The codon is sort of a base tweet apparatus for a certain thread that other tweets point back to. The tweets are on the surface of expression (the timeline) but are all collected together via the codon tweet.
Knovigator quests could supply this infrastructure. The codon is just a quest.
Instead of relying on twitter to incrementally build a thread by using it's interface in an unorthodox way and then teach people how to read twitter in this unorthodox way, we can move back and forth between knovigator.
In the past I've tried to develop exclusively on twitter by stacking threads into "skeins." https://twitter.com/AGWilsonn/status/1189295773873258497?s=20
It occurs to me that very few people care about this kind of iteration. I could just as easily re-publish each time. Even if there is some repetition most people probably didn't see the tweet in the timeline in the first place, and even less probably read all the way. If they did, they might just be invested in the development anyway.
What you lose is the conversation about the tweets every time you re-publish. Each thread is fresh instead of contextual. But, if they want to engage, they can just do that on knovigator. And of course, my knovigator development will reflect the feedback that I received on twitter.
if you have embedded another person's tweets into your thread you might want to be careful how often you re-publish from knovigator because they would get notified every time and that might get annoying.
hierarchical streams