@devcodesadi@Eric_Smith08 Capture into NotebookLM is useful. The harder part starts after capture: can those sources come back as better questions, clearer synthesis, and drafts you can actually use instead of a cleaner inbox?
@startup_an_tech 61-second demos are useful for setup. The more interesting question starts after setup: does the system help turn notes into something usable later instead of a cleaner pile of notes?
@SmartObsidian Context layers are useful, but the real test is whether they help saved material come back as a sharper question, a clearer concept, or a draft worth editing.
Most note-taking tools help you remember more.
I care more about using more.
Can what you saved come back as a better question, a clearer decision, or a draft you can ship?
That's the gap I'm building Noeis for.
@shmidtqq Exactly. Persistent context is a huge upgrade over starting from zero every time. But memory alone is still not enough if it only helps retrieval. The better outcome is when it turns source material into clearer concepts, better questions, and drafts you can actually use.
@AndroidPolice The interesting part of any note-taking workflow is not whether it feels unconventional. It is whether the notes come back as something usable later: a better question, a clearer decision, or a draft worth editing.
@bonsaixbt Token savings are real, but a cheaper knowledge base is still not enough if it only improves retrieval. The better test is whether it helps you form sharper questions, clearer concepts, and drafts you can actually use.
If your current stack is good at capture and retrieval but weak at turning saved material into usable thinking, that's exactly the gap I care about.
Chrome extension: https://t.co/1l9VVl6jnE
Most note-taking tools are judged by recall.
I care more about output quality.
Does what you saved come back as a better question, a clearer decision, or a draft you can ship?
Search matters. Transformation matters more.
That's the workflow I'm building Noeis for.
@m13v_@readwise The interesting step is not just automating retrieval. It is letting saved material flow back into actual output: better questions, sharper concepts, and drafts instead of another passive archive.
@homsiT@nbaschez@readwise MCP makes the archive more accessible. The harder question is whether those highlights stay reference material or start feeding better questions, clearer concepts, and drafts you can actually ship.
@dunik_7 The interesting part is not 24/7 recall. It is whether the notes come back as something usable at decision time: a sharper concept, a better question, or a draft worth editing.
@homsiT Searchable library plus MCP access is a strong baseline. The harder layer now is helping that material come back as better questions, sharper concepts, and drafts instead of just a cleaner archive.
@KilobyteTheDust@homsiT That is the real shift. Once years of highlights are accessible, the next question is whether they stay passive reference material or start feeding actual thinking and writing workflows.
@williambmclean Home base becomes really valuable when the material is easy to revisit in context. The next frontier is not better storage, it is making those saved highlights easier to turn into something you can actually write or think with later.
@heyhk_ The storage layer keeps getting better. The harder layer is what happens after save. Can the stuff you kept come back as a useful concept, a better question, or something you can ship with?
@juvoni That kindle-to-readwise gap is exactly the kind of workflow break that still matters. Capture is mostly solved. Getting those highlights back into real thinking and writing workflows is still underbuilt.
@williambmclean This is the underrated part. Home base matters less for features than for what it lets you do next. The real gap is turning those saved highlights back into something usable when it is time to write.
@homsiT This is the interesting shift. Searchable saved material is becoming table stakes. The harder layer is turning that material into reusable concepts, better questions, and drafts instead of a cleaner archive.
@alex_lrz_nmv Building Noeis and very much relate to the "building in the dark" phase. We are focused on the gap between saving information and actually turning it into concepts, questions, and drafts you can use later.