MarkRead

MarkRead Official Account

[MarkRead @MarkReadPro]

@noahduck283 “AI 边写代码还得边写工作日志”这个太真实了。长期偏好放静态知识库、过程记忆交给工具自动处理，这个分层很清楚。

[MarkRead @MarkReadPro]

@avsa Funny how the decentralized dream ended up being a folder of text files and a git log. Plain text really does outlive every platform.

[MarkRead @MarkReadPro]

@karrisaarinen @linear Clean round-tripping would be huge: paste markdown in, export the same markdown out, without tables or nested lists getting mangled.

[MarkRead @MarkReadPro]

Searching “Markdown” finds a dozen editors.
MarkRead is for when the file already exists and you want it to feel like a book.
Get it on iOS → https://t.co/O2yPkGQxnS

[MarkRead @MarkReadPro]

@Yani3rt Nice way to get at a local vault from any browser without syncing it anywhere. Does it render wikilinks and embedded images properly in the read-only view?

[MarkRead @MarkReadPro]

@ZacharyZhang A Markdown editor sitting next to Docs and Sheet makes sense. Curious whether you're going with live preview in the same pane or a split view.

[MarkRead @MarkReadPro]

@kani_zeta 解決済みの内容を省く指示が効きそうですね。Joplinであとから読み返すとき、要点だけ残っていると探しやすいです。

[MarkRead @MarkReadPro]

@tobi462 わかります。Markdownエディタ＋同期ツールとしてしか使っていないなら、Obsidianの重さが気になってくる瞬間ありますね。編集と同期を分けると、かえって身軽になりそうです。

[MarkRead @MarkReadPro]

@stpaquet Keyboard-first search across a plain Markdown folder is such a good fit for a long-lived notes library. Fast enough that the folder structure can stay out of the way.

[MarkRead @MarkReadPro]

@BradGroux @kb1381 @klotzsche_ That’s a great boundary: let the system handle capture, but keep the durable artifact human-readable and portable. A call log you can open in Obsidian years later is much more useful than a locked transcript.

[MarkRead @MarkReadPro]

@tapitapeh The “without leaving the app” part is the magic—capture the thought before a context switch, then keep the durable result as a plain .md file. That’s a really clean workflow.

[MarkRead @MarkReadPro]

Writing in one app. Reading in MarkRead.
Keep drafting where you draft. When it’s time to review the longform, open the .md here.
iOS link → https://t.co/O2yPkGQxnS

[MarkRead @MarkReadPro]

@sama That “learns my workflow and style” loop is where a small local Markdown log could shine: keep the durable context in your own files, and let the agent handle the repetitive edges.

[MarkRead @MarkReadPro]

@melvindvivas Curious about it. The useful test for me is whether capture stays frictionless while notes remain exportable as plain Markdown—easy to trust, easy to move later.

[MarkRead @MarkReadPro]

@nuonome80867 全部をそのまま残すより、会話の結論と次に使えそうなプロンプトだけMarkdownで抜くと、あとで検索したときに助かりそうです。元ログへのリンクも添えると追いやすいですね。

[MarkRead @MarkReadPro]

@AkshayA40831411 @grok Absolutely. DNFing a book is often what makes room for the one you actually want to keep reading.

[MarkRead @MarkReadPro]

@OpenDocScanApp @Amadomartin Keeping context close to the user is what makes local-first feel like a product principle, not just a storage choice.

[MarkRead @MarkReadPro]

@iloveFazz A notes app lives or dies by how quickly ideas become findable again. Hope the Android build nails that loop.

[MarkRead @MarkReadPro]

Dark mode that still feels like paper.

Ink on a quiet surface—not a terminal theme pretending to be a book.

MarkRead on the App Store → https://t.co/O2yPkGQxnS

[MarkRead @MarkReadPro]

@0xtomdaniel @hwchase17 The plain-file approach also makes memory legible and editable instead of a black box. Portability is a huge part of the appeal.