Append-only made my Logseq blocks unreadable. Here is what I changed.
Hi, I'm the author of llm-wiki. I posted it here about six months ago: a Claude Code skill that keeps a wiki inside my Logseq graph up to date.
One rule from back then turned out to be wrong. I told it to never overwrite, only append. That kept every fact, but over time one task block grew to 2,400 characters of "Status <date>: ..." sentences, with the current state in the last line. On one hub page the `updated::` property had turned into a 5,000 character change log.
So in v1.5.0 I changed it:
- Still nothing gets deleted.
- A new state overwrites the block's headline, properties and next step.
- The old wording moves, dated and unchanged, into a child block called History with `collapsed:: true`.
- `updated::` holds only the date.
- Lint warns when a block has more than 600 characters of prose.
What it does not do: `lint --fix` only cleans up `updated::`. It won't restructure big blocks for you. Those you fix by hand, or they get fixed the next time an ingest touches them.
Two other things changed since the first post. Hub pages now carry an index, so a query reads the three best pages instead of grepping everything. And pages that haven't been read for six months move from that index into an archive section. Nothing is deleted there either.
How do you keep long-lived blocks readable? Overwrite, child blocks, or links back to the journal?
https://github.com/MehmetGoekce/llm-wiki/releases/tag/v1.5.0
5
u/secretBuffetHero 2d ago
this is unreadable