MarkRead

MarkRead Official Account

[MarkRead @MarkReadPro]

Now on the Mac App Store, alongside iPhone and iPad.

[MarkRead @MarkReadPro]

MarkRead is now on the Mac App Store.

Open a folder of Markdown and just read: clean typography, 19 paper themes, multi-page spreads.

With Pro, add a folder as a Reading Set and it follows you to iPhone and iPad, picking up at the same paragraph.

https://t.co/POaNtWWES9

[MarkRead @MarkReadPro]

@yifanxu_ephai 同感。交接时与其让新 agent 读完整聊天记录，不如只给一份简短的“已验证/未验证”清单，再让它对照 agents.md 的硬规则先跑一遍 diff 检查，很多这种补丁能更早被拦下。

[MarkRead @MarkReadPro]

@SeanMombo Ha, totally fair. README.md was basically the gateway drug: plain text that still reads fine raw, which is probably why it ended up everywhere from notes to docs.

[Chandu Thota @ChanduThota]

We are making Markdown files work natively across Google Drive and Docs.

You can now preview .md files in Drive, open them in Docs, edit them, comment on them, and collaborate without converting the file into a Google Doc!

[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で抜くと、あとで検索したときに助かりそうです。元ログへのリンクも添えると追いやすいですね。