i built for this. you can start separate threads, and then can branch off of each post in the thread into its own thread, like an outline of threads.
Conversation
here is an example thread:
1
1
i also built a twitter integration so that each thread can be posted to twitter as a tweetstorm like this:
Quote Tweet
Composed with @knovigator : knovigator.com/quest/i-chemis
Show this thread
2
2
I don't think this will work on twitter this way. You need a way to a) work within the twitter interface, like a hashtag b) pull in historical tweets after the fact since most people face this problem AFTER they've accumulated tweets they now want to curate
1
cool, thank you for the feedback. im planning to build b. can you elaborate on a with an example?
1
I'd like to search twitter for term "mediocrity" by me, and go through all my past tweets and good replies on the theme and very easily file them away into a "quest" and then continue appending with a hashtag or something
2
1
Your key UX issue is the order-from-chaos problem. Until there is critical mass of tweets on a theme, I don't realize it would be worth compiling, nor do I want to put in the overhead work of doing so.
2
2
Yes, I think point b gets us most of the way to your use case. The goal is to sync your tweets and be able to search through them to easily incorporate them into quests. Then publish back out to twitter, in a way mirroring the content there.
1
The advantage of having a separate account is that i can pull in other sources besides twitter so it acts as my personal knowledge base and can pull content from other services including Google Docs, regular websites, etc. and acts as my personal knowledge base.
3
1
From this knowledge base I should be able to aggregate all platforms, recombine information, and broadcast back out to all of them simultaneously if I want while keeping a curated repository of what ive learned/done.
1
I built a product very similar in concept to your knovigator back in 2009-11 at Xerox: trailmeme (google images should still have views). HTML5 visual "trail" (== quest) maps compiled via search results and a browser extension.
It deadpooled in part (this is my analysis) that only a very tiny fraction of potential users have the curatorial drive to use meta products. A competitor to trailmeme at the time, pearltrees, is still limping along. This is an uncanny valley zone in product design space.
1
1
3
You can either add specialized vertical toolchain bits for sectors like education and healthcare to go niche, or you can get really ambitious and try to invent a native social medium around your quests. We tried both with trailmeme. Neither worked.
1
2
Show replies

